Data preparation and quality

Normalize campaign attribution

Extract prioritized UTM or campaign parameters and map aliases.

Available recipeIncludes configuration, sample data and tests

Make it your own

Review the setup and limits below, then open an editable copy in Turbyn.

Use this recipe

Your selection stays with you through signup.

What it does

URL decoding and configured precedence for utm_campaign, hs_campaign_id, and campaign.

What to customize

Configure aliases and precedence.

Run the included tests with your configuration and mappings. Review success, missing-input and failure results before publishing.

Expected outcome

This included example runs in dry-run mode with synthetic data. Integration tests separately cover provider responses using test doubles. It is not a live customer result.

Sample input

sample-input.json

{
  "inputFields": {
    "field1": "utm_source=web&utm_campaign=spring%20sale"
  }
}

Sample output

sample-output.json

{
  "outputFields": {
    "output1": "SPRING-2026",
    "output2": "mapped",
    "output3": "Source utm_campaign; URL fragment ignored; original tracking value remains in field1."
  }
}

Returned fields

output1: canonical campaign
output2: mapped, recognized, missing, or invalid
output3: source and preservation reason

What changes when it runs

Reads field1 query string and returns canonical campaign; preserves source in field1 and performs no external calls.

Ready to try it with your rules?

Map your inputs, test a sample and publish the version you’ve checked.

Use this recipe