Attribution
Give credit for conversions to the sessions and messages before them, using UTM parameters and click IDs, and send credited conversions to ad platforms.
Last reviewed September 15, 2026
Data → Data Preferences → Attribution: the sources, tracking parameters, lookback window and results of multi-touch attribution for your workspace.
Attribution gives credit for each conversion to the marketing touchpoints that came before it. Vendo builds the touchpoints from your event data. Then it calculates six attribution models in one run and writes the result to your warehouse.
Where attribution lives in Vendo
| Part | Where | What it does |
|---|---|---|
| Attribution page | Data → Data Preferences → Attribution | Sources, tracking parameters, lookback window and results for your workspace |
| Conversion destinations | The Attribution section of an ad platform destination | Selects which model value Vendo sends to the ad platform |
| Attribution models | Attribution Models | Explains how each model divides credit |
| Channel Grouping | Data → Data Preferences → Channel Grouping | Groups traffic into channels for analysis. Attribution does not use it. |
| Shopify app | Shopify Attribution | Writes first-touch and last-touch values to Shopify customer profiles. It is a separate feature. |
| Measurement | Measurement and Budget | Uses attribution results as one input for cross-channel analysis |
How Vendo builds touchpoints
Each source that you add to the Attribution page has one Touchpoint role.
| Role | Events you select | How Vendo uses them |
|---|---|---|
| Sessions | Attribution events, for example page views and screen views | Vendo groups the events of each user into sessions. Each session is 1 touchpoint. |
| Email / Push engagement | Engagement events, for example email opens and push clicks | Each event is 1 touchpoint. Vendo credits it to the Channel that you select: Email, Push, SMS or In-app. |
| Conversions | Conversion events, for example order_placed | These events get the credit. You must have exactly 1 conversion source. |
Ad platform sources do not contain user-level data. Thus you cannot add an ad click as a touchpoint. Vendo reads the click IDs and UTM parameters on your session events instead.
Sessions
A new attribution session starts after 30 minutes with no events from the same user and source. Vendo keeps the first value of each tracking parameter in the session.
The Sessions page in Data Preferences has a Session timeout (minutes) setting and an Excluded events list. The attribution engine does not read these settings. Attribution sessions always use the 30-minute gap.
Channel and platform
For each touchpoint, Vendo sets a platform in this order:
- An engagement touchpoint gets the Channel of its source.
- A session with a click ID gets the platform of that click ID.
- A session with a
utm_sourcevalue gets that value as its platform.
A session with no click ID and no utm_source value does not get credit. A touchpoint gets credit only when it occurs inside the lookback window before the conversion.
Click IDs
Vendo reads these click parameters. The labels are the labels on the Configuration tab.
| Label | Parameter |
|---|---|
| Google Ads (gclid) | gclid |
| Meta Ads (fbclid) | fbclid |
| Microsoft Ads (msclkid) | msclkid |
| TikTok Ads (ttclid) | ttclid |
| Twitter/X Ads (twclid) | twclid |
| Snapchat Ads (sccid) | sccid |
| Display & Video 360 (dclid) | dclid |
| Kochava (ko_click_id) | ko_click_id |
| LinkedIn Ads (li_fat_id) | li_fat_id |
| Google Web-to-App (wbraid) | wbraid |
| Axon Ads (aleid) | aleid |
You can also add a custom click parameter. Vendo uses its name as the platform name.
UTM parameters
Vendo can read utm_source, utm_medium, utm_campaign, utm_term, utm_content, utm_id, utm_source_platform, utm_creative_format, utm_marketing_tactic and utm_creative. The results use utm_campaign as the campaign and utm_source as the source.
Settings on the Attribution page
The page header has a status list and the Run Attribution button. The status list has 2 values: Active and Paused. The page has 3 tabs: Configuration, Field Mapping and Results.
Configuration tab
These settings apply to all sources. Click Save Configuration to save them.
| Setting | What it does | Default |
|---|---|---|
| Attribution Model | Your preferred model: Last click, First click, Linear or Position-based. Vendo calculates all models in each run, so this choice does not change the Results tab. | Last click |
| Lookback Window | The number of days before a conversion in which a touchpoint can get credit. Enter 1 to 90. | 7 days |
| Timezone | The timezone of the conversion dates and session dates in the results. | The timezone of your workspace, or UTC |
| First Conversion Only | Counts only the first conversion of each user. | On |
| Use Identity Resolution | Uses the identity graph to join the events of one user across devices and platforms. | On |
| UTM parameters | The UTM parameters that Vendo reads from session sources. | All selected |
| Click parameters (built-in) | The click parameters that Vendo reads from session sources. | All selected |
| Custom click parameters | Your own click parameter names. Map each one on the session source card. | None |
A custom click parameter name must start with a letter. It can contain only letters, digits and underscores.
Field Mapping tab
Click Add source to add a source. The menu shows your connected sources, Custom table and Connect a new source…. You can add up to 10 sources.
Each source card has these fields:
| Field | What it does |
|---|---|
| Source label | The name of the source in the results |
| Touchpoint role | Sessions, Email / Push engagement or Conversions |
| Source table | The table to read. Only for a custom table. |
| User identifier | The column that identifies the user |
| Event name field | The column that holds the event name |
| Event timestamp field | The column that holds the event time |
| Attribution events | Sessions only. The events that count as session activity. |
| Tracking parameters (UTM + Click IDs) | Sessions only. The column for each UTM parameter and click parameter. |
| Channel and Engagement events | Email / Push engagement only |
| Conversion events and Conversion value property (optional) | Conversions only |
For some connected sources, Vendo fills the mappings when you select the role. The card then shows Auto-mapped. Click Customize to change the columns.
| Role | Sources with default mappings |
|---|---|
| Sessions | Mixpanel, Amplitude, Web Tracking |
| Email / Push engagement | Klaviyo, Customer.io, OneSignal, Braze |
| Conversions | Mixpanel, Amplitude, Shopify, Stripe |
On a session source, Auto-match fills each empty tracking parameter. It uses a column with the same name. If no column matches and the table has a properties column, it uses properties.<parameter>.
Click Save sources to save the sources. You cannot save without exactly 1 conversion source.
Results tab
The Results tab shows these items:
| Item | What it shows |
|---|---|
| Lookback list | The lookback for the results: 7, 14, 30, 60 or 90 days, and your saved lookback. The badge Live · N-day shows live results. |
| Total Conversions | The number of unique conversions |
| Total Value | The sum of the Participation values. A conversion with 3 touchpoints adds its value 3 times. |
| Unique Users | The number of users with conversions |
| Avg Touchpoints | The average number of touchpoints for each conversion |
| Attribution by Platform | The conversions and the credited value of each model for each platform |
| Configuration Summary | Your current attribution settings |
When you select a lookback, Vendo calculates the results again for that lookback. If the live results are not available, the tab shows the results of the last run.
When attribution runs
When the status is Active, Vendo runs attribution one time each day. When the status is Paused, Vendo skips the run.
To start a run now, click Run Attribution. The message that shows has a View run link to the run in Activity Logs.
A run fails if a source table is not found. It also fails if a source table had no new data for more than 7 days.
Where attribution results go
- Results tab: the summary and the platform table on the Attribution page.
- Warehouse: Vendo writes the results to the
attribution_summarytable in your dataset. You can query it in the SQL Editor. - Ad platforms: conversion destinations send the credited conversions to the ad platform.
- Measurement: the click path signal in Measurement and Budget reads the attribution results. The Agent and the MCP server can read unified attribution through the
measurement_unified_attributiontool.
Attribution on conversion destinations
The conversion destinations for Google Ads, Meta Ads, TikTok Ads, Snap Ads, Microsoft Ads, Pinterest Ads, LinkedIn Ads and X Ads have an Attribution section.
| Setting | What it does | Default |
|---|---|---|
| Attribution Model | Selects which model value Vendo sends: Participation, Linear, U-Shaped, First Click, Last Click or Time Decay | Last Click |
| Lookback Window | Sets how many days of conversions each export reads again: 28 days, 14 days, 7 days or 1 day | 7 days |
The credit comes from the attribution run, which uses the Lookback Window on the Attribution page. Participation gives full credit to each touchpoint, so the ad platform can get more than 1 conversion for each purchase.
The Axon Ads destination has its own Attribution Model and Lookback Window (hours) fields. Vendo sends these values to Axon.
For the steps on each platform, see the export conversions pages for Google Ads, Meta Ads, Microsoft Ads, TikTok Ads and Snap Ads.
Channel Grouping
Data → Data Preferences → Channel Grouping lists your grouping models. When you first open the page, Vendo creates the Default Channel Grouping model. It has channels such as Google Ads, Organic Search, Email, Referral and Direct.
Attribution does not use Channel Grouping. The platform in the attribution results comes from click IDs, utm_source and the engagement channel. For more information about grouping models, see Grouping Rules.
Set up attribution
Before you start, connect a source with page view events and a source with conversion events.
- Go to Data → Data Preferences → Attribution.
- Click the Field Mapping tab.
- Click Add source.
- Select the source that has your page view events.
- In Touchpoint role, select Sessions.
- In Attribution events, add your page view and screen view events.
- If the card does not show Auto-mapped, select the User identifier, Event name field and Event timestamp field columns.
- In Tracking parameters (UTM + Click IDs), click Auto-match.
- Make sure that each click parameter you use has a column.
- Click Add source, then select the source that has your conversion events.
- In Touchpoint role, select Conversions.
- In Conversion events, add the events that count as conversions.
- If the conversion has a value, select the Conversion value property (optional).
- Click Save sources.
- Click the Configuration tab.
- Set the Lookback Window and the other settings.
- Click Save Configuration.
- In the status list, select Active.
- Click Run Attribution.
- When the run completes, click the Results tab.
Troubleshooting
| Problem | Cause | Solution |
|---|---|---|
| Run Attribution is not available | The status is Paused, or you have no conversion source | Select Active. Add a source with the Conversions role and click Save sources. |
| The Results tab shows “No attribution data yet” | No run completed, or no conversion matched a touchpoint | Click Run Attribution. Check the run in Activity Logs. |
| The run fails with a table problem | A source table is missing, or it had no new data for more than 7 days | Make sure the source imports data. Then run attribution again. |
| Conversions get no credit | The sessions have no click ID and no utm_source value, or they are outside the lookback window | Map the click parameters and utm_source on the session source. Make sure your links carry UTM parameters. |
| A click ID is not used | The parameter is not selected on the Configuration tab, or it has no column on the session source | Select the parameter. Map its column in Tracking parameters (UTM + Click IDs). |
The platform shows a value such as newsletter | The session had no click ID, so Vendo used its utm_source value | Use the same utm_source values in all your links. |
| Each conversion has a value of 1 | No Conversion value property (optional) is set, or the value is not a number | Select a numeric property on the conversion source. |
| Some conversions are missing | The conversion value is 0 or less, or First Conversion Only is on | Check the value property. Turn off First Conversion Only to count repeat conversions. |
| One user shows as more than one user | Use Identity Resolution is off, or the identity graph has no mapping for the user identifier | Turn on Use Identity Resolution. Check the mappings on the Identity Graph page. |
| A destination says attributed conversions will use a value of 1.0 | The destination source is not a conversion source on the Attribution page | Add that source with the Conversions role. |
| Total Value is higher than your revenue | Total Value adds the Participation value of each touchpoint | Use a model column in Attribution by Platform for credited revenue. |