Who this is for / When to use
This article is for Kyrios users building automations that depend on lead source data, especially when using call tracking, dynamic number insertion, paid ads, or multi-channel marketing.
Use this when a workflow needs to behave differently based on how a contact first or most recently engaged with the business.
What contact attribution variables are
Contact attribution variables are system fields that store how a contact entered or last interacted with the business. Kyrios tracks both First Attribution (original source) and Last Attribution (most recent source) and exposes these values inside workflows for conditional logic and personalization.
Available attribution data includes session source, UTM parameters, campaign, medium, and keyword values.
Step 1: Create a workflow with an incoming call trigger
A workflow trigger defines when contacts enter the workflow. For call-based attribution logic, the trigger must be set to incoming calls.
Navigate to Automation → Workflows.
Click + Create Workflow.
Select Call Status as the trigger.
Set Call Direction to Incoming.
Save the trigger.
Step 2: Add an If/Else condition using attribution data
If/Else conditions allow workflows to branch based on attribution values stored on the contact.
Click + Add Action.
Select If / Else from Internal actions.
Set the action name (for example, "Condition").
Step 3: Select attribution fields in the condition
Attribution fields are accessed through Contact Details and the Attribution category.
In the condition builder, select Contact Details.
Choose Source.
Set the operator to Is.
Open Attribution.
Choose First Attribution or Last Attribution.
Select Session Source.
Step 4: Define attribution values (example: Paid Search)
Attribution values determine which branch the contact follows.
Add a segment under the condition.
Select Session Source (First Attribution) or Session Source (Last Attribution).
Set the condition to Is.
Choose Paid Search from the dropdown.
Save the action.
Name this branch Yes to indicate the contact came from paid ads.
Step 5: Add actions for the matching attribution path
Actions placed under the Yes path apply only to contacts that meet the attribution condition.
For paid ad tracking, a common action is sending conversion data to Google Ads.
Under the Yes branch, click + Add Action.
Select Google AdWords.
Choose the appropriate conversion.
Click Save Action.
Step 6: Publish the workflow
Workflows do not run until published.
Review both Yes and No branches.
Toggle the workflow from Draft to Published.
Once published, incoming calls will be evaluated using attribution data and routed through the correct workflow path.
Common issues and fixes
Attribution data is empty
Cause: The contact did not enter through a tracked source. Fix: Confirm call tracking or UTM tracking is enabled and that traffic sources are properly configured.
Wrong attribution source detected
Cause: Using Last Attribution when First Attribution is required (or vice versa). Fix: Verify whether the workflow should reference original discovery or most recent engagement.
Condition never evaluates to Yes
Cause: Mismatch between attribution field and value. Fix: Re-check the selected attribution field and ensure the dropdown value exactly matches the expected source.
Pro tips
Use both First Attribution and Last Attribution in separate branches for full funnel visibility.
Store attribution values in tags or custom fields if they are needed in later workflows.
Combine attribution conditions with call status or campaign data for more granular routing.
Use Internal Notifications with Custom Values to alert teams of lead sources in real time.
FAQs
Can attribution data be used for both paid and organic sources?
Yes. Attribution conditions can evaluate paid search, organic search, social media, referrals, and direct traffic.
What is the difference between first and last attribution?
First attribution identifies the original source that introduced the contact. Last attribution reflects the most recent source before the current action.
Can this workflow be used for non-call triggers?
Yes. The same attribution logic applies to form submissions, bookings, and message-based triggers.
Can attribution values be inserted into messages?
Yes. Attribution fields can be inserted into emails, SMS, or internal notifications using Custom Values.