-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Scala Common Enrich: add support for non-GA campaign attribution: phase 1 #402
Comments
To be followed eventually by #436 (but much lower priority) |
Note: this ticket covers the batch (Hadoop) flow only. |
Assigning this to Fred. |
Hi @fblundun! Can you update the YAMLs in this ticket to be JSONs? That would be helpful for me... |
The update has been made. |
Thanks Fred! |
alexanderdean
added a commit
to snowplow/iglu-central
that referenced
this issue
Jul 25, 2014
fblundun
added a commit
that referenced
this issue
Sep 3, 2014
alexanderdean
changed the title
Add support for non-GA campaign attribution: phase 1
Scala Common Enrich: add support for non-GA campaign attribution: phase 1
Sep 19, 2014
fblundun
added a commit
that referenced
this issue
Sep 24, 2014
fblundun
added a commit
that referenced
this issue
Sep 24, 2014
fblundun
added a commit
that referenced
this issue
Sep 24, 2014
fblundun
added a commit
that referenced
this issue
Sep 24, 2014
peel
pushed a commit
to snowplow/emr-etl-runner
that referenced
this issue
May 26, 2020
peel
pushed a commit
to snowplow/emr-etl-runner
that referenced
this issue
May 28, 2020
oguzhanunlu
pushed a commit
to snowplow/common-enrich
that referenced
this issue
May 29, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Create a new enrichment in the config.yml like this - standard Google-style settings:
To use it for standard Omniture:
Or to use in a heterogenous environment (different variables are used for different events):
In the case that multiple options are found in the same querystring (e.g.
utm_campaign
andcid
), the first one listed in the YAML will take precedence.See #435 for design discussion.
The text was updated successfully, but these errors were encountered: