UTM Tracking
Pass campaign parameters into Aura schedulers and understand how Aura preserves them
UTM Tracking
UTM parameters identify the campaign that brought a visitor to Aura. When the parameters reach a hosted booking page or supported embed, Aura preserves them with the visitor, lead, and booking so you can analyze source performance.
UTM tracking does not need to be enabled separately for each scheduler.
Supported parameters
| Parameter | Purpose | Example |
|---|---|---|
utm_source | Traffic source | meta, google, newsletter |
utm_medium | Marketing medium | paid-social, cpc, email |
utm_campaign | Campaign name | q3-demo |
utm_term | Keyword or audience | sales-software |
utm_content | Creative or link variation | video-a |
utm_id | Campaign identifier | 238512345 |
ref | Partner or referral reference | partner-acme |
Parameter names are case-sensitive. Use lowercase names exactly as shown.
Hosted schedulers
Add parameters to the URL you place in the ad, email, or campaign:
https://app.aura-app.ai/acme/demo?utm_source=meta&utm_medium=paid-social&utm_campaign=q3-demo&utm_content=video-aAura reads the parameters when the booking journey loads. You do not configure
utm_source or other UTM fields on the scheduler itself.
Embedded schedulers
The UTMs usually live on the host page, while the scheduler runs inside an iframe. The host page must therefore pass its attribution context into Aura. Use Aura's official embed script so supported parameters, click identifiers, and consent state can be passed safely.
For example, if the visitor lands on:
https://example.com/book?utm_source=meta&utm_campaign=q3-demothe embed should pass those values into the Aura scheduler even though its iframe URL is on a different domain. See Embedding for the supported installation.
Avoid building a custom iframe that copies only the visible URL once. It can lose attribution during client-side navigation and cannot communicate later consent changes correctly.
How Aura carries UTMs into a booking
Aura can encounter the same attribution at several stages of the journey. When the booking is created, it resolves the available values in this order:
- Attribution already stored on the lead.
- Attribution supplied with the booking request.
- Attribution stored on the linked visitor session.
This recovery chain helps preserve the original campaign when the booking flow spans several steps. It cannot recover parameters that never reached Aura.
Consent and campaign details
Aura keeps the UTMs and click identifiers that reach it whatever the visitor chooses about advertising. They are your record of how the visitor arrived.
The visitor's choice decides whether Aura uses advertising cookies and whether it shares the booking with your ad partners, such as Meta or Hyros. A refusal or a Global Privacy Control signal stops that sharing. The campaign details stay on the booking.
For embedded schedulers, the host page must pass a supported consent decision as well as the attribution values. Simply adding UTMs to an iframe URL does not grant consent.
Where to view attribution
You can inspect attribution on the lead or call and use Analytics → Attribution to compare sources, campaigns, conversion quality, and revenue. The exact fields shown depend on what reached Aura during the visitor's journey.
UTMs also contribute to ad-performance reconciliation, but they are not the only matching signals. Meta click IDs and browser identifiers can provide a more direct match when available. See Meta CAPI and Ad Tracking for the complete conversion flow.
Naming recommendations
Use a consistent, lowercase vocabulary so one channel does not fragment across several rows:
| Field | Recommended | Avoid |
|---|---|---|
| Source | meta | Meta, facebook, and fb for the same source |
| Medium | paid-social | Mixing cpc, social, and paid arbitrarily |
| Campaign | q3-demo | Spaces and frequently changing labels |
| Content | video-a | Reusing one value for every creative |
Keep a campaign register outside Aura if several people build links. Aura preserves the values it receives; it does not correct inconsistent campaign naming afterward.
Troubleshooting missing UTMs
1. Inspect the exact entry URL
Confirm that the link actually contains the expected lowercase parameters. Test the URL from the ad or message, not a manually reconstructed version.
2. Follow redirects
A short link, landing-page redirect, or authentication hop can remove query parameters. Confirm they are still present when the Aura page or embed loads.
3. Check the embed boundary
If Aura is embedded, confirm the official embed passes host-page attribution. The iframe cannot automatically read the parent page's URL because browsers isolate different domains.
4. Check the advertising choice
A visitor's advertising choice does not remove UTMs. If a booking has its UTMs but Meta or Hyros never received it, the visitor probably declined advertising or their browser sent a Global Privacy Control signal. Aura keeps the campaign details and does not share that booking, which is expected.
5. Check session continuity
A visitor may click an attributed link, leave, and later return through a clean or bookmarked URL. If that return is not connected to the stored visitor journey, the later booking may be unattributed.
6. Distinguish UTM capture from event routing
Per-link Meta settings decide which pixel receives which conversion event. They do not switch UTM parsing on or off. A link can send a conversion without UTMs, and it can store UTMs even when a particular Meta event is disabled.
Frequently asked questions
Does every scheduler capture UTMs?
Yes, when supported parameters reach Aura. There is no separate UTM-enable setting for a new link.
Why did one day capture UTMs and the next day not?
The link can be the same while the journey differs. Compare the actual entry URL, redirects, embed context, and whether the booking remained connected to the original visitor session.
Can Aura restore a UTM that a redirect removed before Aura loaded?
No. Aura can recover values from its own stored lead or visitor journey, but it cannot infer a campaign parameter it never received.
Are UTMs what deduplicate Pixel and CAPI events?
No. Aura uses a shared event name and stable event ID for Meta deduplication. UTMs help explain campaign origin; they are not the deduplication key.