Skip to content
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

Closed
alexanderdean opened this issue Oct 24, 2013 · 6 comments
Assignees
Milestone

Comments

@alexanderdean
Copy link
Member

Create a new enrichment in the config.yml like this - standard Google-style settings:

{
    "schema": "iglu:com.snowplowanalytics.snowplow/campaign_attribution/jsonschema/1-0-0",

    "data": {

        "name": "campaign_attribution",
        "vendor": "com.snowplowanalytics.snowplow",     
        "enabled": true,
        "properties": {
            "mapping": "static",
            "fields": {
                "mktMedium": ["utm_medium"],
                "mktSource": ["utm_source"],
                "mktTerm": ["utm_term"],
                "mktContent": ["utm_content"],
                "mktCampaign": ["utm_campaign"],
            }
        }
    }
}

To use it for standard Omniture:

{
    "schema": "iglu:com.snowplowanalytics.snowplow/campaign_attribution/jsonschema/1-0-0",

    "data": {

        "name": "campaign_attribution",
        "vendor": "com.snowplowanalytics.snowplow",     
        "enabled": true,
        "properties": {
            "mapping": "static",
            "fields": {
                "mktMedium": [],
                "mktSource": [],
                "mktTerm": [],
                "mktContent": [],
                "mktCampaign": ["cid"],
            }
        }
    }
}

Or to use in a heterogenous environment (different variables are used for different events):

{
    "schema": "iglu:com.snowplowanalytics.snowplow/campaign_attribution/jsonschema/1-0-0",

    "data": {

        "name": "campaign_attribution",
        "vendor": "com.snowplowanalytics.snowplow",     
        "enabled": true,
        "properties": {
            "mapping": "static",
            "fields": {
                "mktMedium": ["utm_medium", "medium"],
                "mktSource": ["utm_source", "source"],
                "mktTerm": ["utm_term", "legacy_term"],
                "mktContent": ["utm_content"],
                "mktCampaign": ["utm_campaign", "cid", "legacy_campaign"],
            }
        }
    }
}

In the case that multiple options are found in the same querystring (e.g. utm_campaign and cid), the first one listed in the YAML will take precedence.

See #435 for design discussion.

@alexanderdean
Copy link
Member Author

To be followed eventually by #436 (but much lower priority)

@alexanderdean
Copy link
Member Author

Note: this ticket covers the batch (Hadoop) flow only.

@alexanderdean alexanderdean added this to the JSON-powered enrichments milestone Jun 3, 2014
@alexanderdean
Copy link
Member Author

Assigning this to Fred.

@fblundun fblundun removed this from the JSON-powered enrichments milestone Jun 16, 2014
@alexanderdean
Copy link
Member Author

Hi @fblundun! Can you update the YAMLs in this ticket to be JSONs? That would be helpful for me...

@fblundun
Copy link
Contributor

The update has been made.

@alexanderdean
Copy link
Member Author

Thanks Fred!

fblundun added a commit that referenced this issue Aug 29, 2014
fblundun added a commit that referenced this issue Sep 1, 2014
@alexanderdean alexanderdean added this to the Version 0.9.9 milestone Sep 19, 2014
@alexanderdean 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 fblundun added this to the Fred Kinesis 1 milestone Oct 10, 2014
@fblundun fblundun modified the milestones: Version 0.9.9, Fred Kinesis 1 Oct 10, 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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants