source-klaviyo-native: support custom event streams with user-defined filters#3795
Draft
source-klaviyo-native: support custom event streams with user-defined filters#3795
Conversation
… filters
Allow users to create additional event streams with custom filters. Each
custom stream captures events matching the specified filters and is
named with a 'custom_' prefix to prevent naming collisions with connector
defined streams.
Supported filters:
- metric_id: equals(metric_id,"<value>")
- profile_id: equals(profile_id,"<value>")
- profile: has(profile,"<value>")
At least one filter must be provided per custom stream. Custom streams use
dynamically created Events subclasses with the filters set via the model's
additional_filters class variable.
Example config:
advanced:
custom_event_streams:
- name: "my_metric_events"
metric_id: "BAdaPPL"
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description:
Allow users to create additional event streams with custom filters. Each custom stream captures events matching the specified filters and is named with a 'custom_' prefix to prevent naming collisions with connector defined streams.
Supported filters:
equals(metric_id,"<value>")equals(profile_id,"<value>")has(profile,"<value>")At least one filter must be provided per custom stream. Custom streams use dynamically created Events subclasses with the filters set via the model's
additional_filtersclass variable.Snapshot changes are expected due to the custom event stream related fields added to the spec and the example custom event streams I added to
config.yamlto exercise the discovery logic.Workflow steps:
(How does one use this feature, and how has it changed)
Documentation links affected:
The connector's documentation should be updated to reflect the new functionality for specifying custom event streams.
Notes for reviewers:
Confirmed custom event streams are discovered as expected - with a
custom_prefix in their names. Confirmed custom event streams go through the same code path as the existingeventsstreams.