Skip to content
AISARAISAR
All articles

Links with UTM tags: where a client came from

How AISAR short links with UTM tags bring a client into a messenger and record where they came from: the supported channels, the other sources AISAR recognises by itself (Telegram bot, Instagram, Messenger, Meta ads), what the first and last touch are, how the tags reach deals, Bitrix24 and amoCRM, and where the limits are.

Clients write to a messenger from a flyer, a newsletter, a website or an ad, and the conversation does not show what brought them. An AISAR link with UTM tags solves this: the client opens it, lands straight in a chat with your number or account, writes, and the contact in AISAR keeps a touch with that link's tags. Touches are available in business companies.

How it works

  1. You create a link: pick a channel and set the utm_source, utm_medium, utm_campaign, utm_content, utm_term tags. AISAR gives you a short address like https://api.aisar.app/l/k7m2x9q1.
  2. You place the address anywhere: on a website, in a QR code on a flyer, in a newsletter, in a profile bio.
  3. The client opens the link and lands straight in the messenger of the chosen channel. For WhatsApp and Telegram the input box already holds a text with the link's short code; for a Telegram bot the "Start" button appears.
  4. The client sends the message. AISAR recognises the link and records a touch: which link, which tags, into which channel and in which conversation.
In the cabinet touches are called contacts or visits: "Contacts" in the link list, "All contacts" in the contact card. It is the same thing.

Where to find the links

Open "Settings", the "Connections" section, the "UTM links" item: it comes right after "Channels". The item shows in business companies for those allowed to view links. The page lists the active links; the "Show archived" switch adds the archived ones. The same is available through the API: the UTM tracking links group.

Role permission (the "UTM links" section)What it allowsStandard roles
ViewSee the list, copy linksAdministrator, manager, agent
CreateThe "Create link" buttonAdministrator, manager
Edit and archive"Edit", "Archive", "Restore"Administrator, manager
Delete"Delete forever" for an archived linkAdministrator

Those who can only view see a hint above the list: "You can view and copy links. Admins and managers create and change them." Custom roles are covered in Setting up roles.

Creating a link

  1. Click "Create link". The "New link" panel opens.
  2. "Where the link leads": pick a channel. Connected WhatsApp, Telegram, Instagram and Messenger channels fit. The channel cannot be changed later. If there are no suitable channels, the panel suggests connecting one in "Channels".
  3. "Name": for example "Instagram, November stories". Only you and your team see it, never the client; the same name later shows on the contact card.
  4. "UTM tags": utm_source, utm_medium, utm_campaign, utm_content, utm_term, all optional. Suggestions come from your earlier links, so the tags of different links are spelled the same way.
  5. For WhatsApp and Telegram: "Text the client sends first" and the "Add the link code to the text" switch. A code like #kq7m2x9p is added at the end of the text, AISAR recognises the link by it. With the code off, AISAR counts clicks only, and which clients came through the link stays unknown.
  6. Click "Create link" at the bottom of the panel. The "The link is ready" block appears: the "Short link" with a copy button and the "What the client gets" preview showing what opens for the client and which text is in the input box. A QR code can be made from the same link.
  • Copying. Every active link in the list has a "Copy link" button. Next to it are the "Clicks" and "Contacts" counters.
  • Editing. "Edit" in the link menu opens "Edit link": the name, tags and text can change, the channel and the code cannot, because the link may already run in ads.
  • If the channel is down, the link gets a mark ("Channel disconnected", "Channel address missing", "Channel not supported"), and the client sees "Page not found". Reconnect the channel in "Channels".

Supported channels and what the client sees

ChannelWhere the link leadsHow AISAR recognises the link
WhatsApp (by QR) and WhatsApp BusinessA chat with your number, the input box holds a ready text ending with a code like #k7m2x9q1By the code in the text the client sent
Telegram (account) and Telegram BusinessA chat with the account by username or number, a text with the code, as for WhatsAppBy the code in the text
Telegram botA chat with the bot and the "Start" buttonTelegram itself passes the link code to the bot when the client taps "Start"; the AISAR conversation shows a /start message
Instagram (via Meta)Your account's DirectMeta passes the link code along with the first message of a new conversation
Facebook MessengerA chat with your pageThe same way as Instagram

You can set your own text for WhatsApp and Telegram, up to 300 characters, for example "Hello! I would like to know about the offer". The #… code is added at the end automatically. It can be turned off, but then no touch is recorded for WhatsApp and Telegram: AISAR has nothing to recognise the link by. Links to Threads, live chat, telephony and email are not available.

Other sources AISAR recognises by itself

  • Meta ads. If the client wrote by tapping a "message on WhatsApp" ad, or an ad in Instagram or Messenger, AISAR records a touch with utm_source = meta_ads, utm_medium = paid_social, and puts the ad headline into utm_content. utm_campaign stays empty: the messenger does not pass the campaign name. For WhatsApp connected by QR, a touch from an ad is recorded only if WhatsApp passed the ad click identifier.
  • Your own deep links to a bot, Instagram or Messenger. If the client came through a link like t.me/<bot>?start=…, ig.me/m/<account>?ref=… or m.me/<page>?ref=… made outside AISAR, a touch is recorded too, but without UTM tags: it holds only the parameter value (Latin letters, digits, _, -; up to 64 characters for a Telegram bot, up to 255 for Instagram and Messenger, where = is allowed too). For a Telegram bot this means such a visit now creates a conversation with a /start message. A plain /start without a parameter still creates no conversation.

First and last touch

One client can come several times: first from an ad, a month later from a flyer. Touches pile up in the contact's history, and AISAR singles out two of them: the first (where the client came from originally) and the last (what brought them now). A touch never changes once recorded, the first one is never overwritten. When duplicates are merged, the touches of both contacts gather on the one that remains.

  • AISAR deals. A deal has five UTM fields. A deal from an auto-lead gets the tags of its conversation's touch, or, if there is none, of the contact's last touch. A deal created by hand without tags gets the tags of the contact's last touch. If at least one tag is set on creation, AISAR fills in nothing.
  • Scenarios. The tags of the last touch are available as the variables {{contact.utm_source}}, {{contact.utm_medium}}, {{contact.utm_campaign}}, {{contact.utm_content}}, {{contact.utm_term}}, and the link name as {{contact.source_link}}. With no touches an empty string is substituted.
  • API and webhooks. The contact card returns the first and last touch in the attribution field, the full history is in GET /v1/contacts/{contact}/touches. When a new touch with tags becomes the first or the last one, a contact.updated webhook goes out.

Where you see where a client came from

  • The "Where they came from" block in the contact card, including the contact panel on the right in the chat. With one touch it shows a "Came via" row; with more, "First" and "Latest". Each row has the source / medium tags, the link name or a "Meta ad" mark with the ad headline, the channel and the date. The "All contacts" button expands the full history. A contact without touches has no such block.
  • The "Ad" link of a Meta ad opens the ad only if the address leads to a Meta site. Otherwise the address is shown as text: for WhatsApp connected by QR, the sender may set it.
  • The "The client started the bot via a link" chip. When the client tapped "Start" in a Telegram bot through a link, the conversation shows this chip instead of the /start message with the code. Which link it was shows in the "Where they came from" block.
  • Deal. The UTM fields of an AISAR deal carry the hint "Leave empty to take the tags of the contact's latest visit"; filled-in values are marked "Taken from the contact".

Passing to Bitrix24 and amoCRM

If a Bitrix24 or amoCRM integration is connected, the tags go there too. Passing is on by default, integrations connected earlier included. Empty tags are not sent, so values already filled in the CRM are not overwritten.

  • Bitrix24. A lead gets the standard UTM fields of its conversation's touch (or of the contact's last touch), a deal gets the tags of the AISAR deal, a contact gets the tags of the first touch. For a lead you can choose the first touch instead of the conversation's touch. More in Connecting Bitrix24.
  • amoCRM. A deal AISAR creates from an inquiry, straight into the pipeline or into "Unsorted", gets the tags of the conversation's touch (or of the contact's last touch; the first touch can be chosen instead). The tags go into the deal fields with the codes UTM_SOURCE, UTM_MEDIUM, UTM_CAMPAIGN, UTM_CONTENT, UTM_TERM, AISAR creates no fields of its own. If the amoCRM account has no such fields, the tags are not passed and the integration log gets a utm.fields_missing entry. If amoCRM does not accept the values, the deal is still created, only without the tags, and the log gets utm.rejected (utm.unsorted_rejected for "Unsorted").
Where to set itThe switch and the choice
The Bitrix24 integration card ("Settings", "CRM and integrations"), the "Sync settings" tab"Send UTM tags to the Bitrix24 lead, deal and contact" and "Which visit goes to the lead and deal": "This dialog's visit, otherwise the latest" (fits most companies) or "The very first visit" (if you credit sales to the client's first source). The Bitrix24 contact always gets the first visit.
The amoCRM integration card, the "Sync" tab"Send UTM tags to the amoCRM deal" and the same choice of visit. If amoCRM has no UTM deal fields, a warning appears under the switch: turn on the UTM fields in amoCRM deal settings and AISAR starts filling them.

Clicks and touches: what is counted

  • Clicks are how many times the short link was opened. They include the requests messengers make to build a link preview, so the number is approximate and usually higher than the number of clients.
  • Touches are how many times a client actually wrote through the link. A repeat of the same source by the same client within an hour counts as one touch, and at most 10 touches an hour are recorded per client.

Archive and deletion

Archive a link you no longer need ("Archive" in the link menu): it stops opening, the client sees "Page not found", and its code in messages no longer produces touches. If the link runs in an ad, remove it there first. Touches through the link stay on the contact cards. "Restore" brings a link back from the archive. "Delete forever" is available only for an archived link. Only an archived link nobody wrote through can be deleted for good: if it already has touches, it stays archived so that the contacts' history keeps its name. The link code and its channel never change after creation; if you need another channel, create a new link.

Limits

  • The client erased the code. In WhatsApp and Telegram the client can delete or change the text before sending. Without the code no touch is recorded.
  • Instagram and Messenger: new conversations only. The link code comes with the first message of a new conversation. If the client has already chatted with your account or page, following the link gives no touch.
  • The code can be typed by hand. The #… code is visible in the text, so a client can type it themselves. For WhatsApp and Telegram this is built into the mechanism, keep it in mind when analysing.
  • The channel must be connected. If the channel is disconnected, deleted or archived, the link does not open. If the channel's number or username changes, the link leads to the new address right away.
  • What gives no touches. Messages in groups, loading older history, your own outgoing messages and conversations of family (kids) companies.
  • Older conversations. Touches are recorded from the moment the feature launched; they do not appear retroactively for older conversations.

See also