Add UTM tags to the links that send people to your directory, and PartnerPage saves them with each contact request and matchmaking request those visitors send. You then see which campaign, email or ad brought each request, in your CSV exports, your webhooks and the API. This article is for vendors and developers.
Who can do this: anyone can add UTM tags to links; Admin and Manager roles export requests · Availability: all directories with contact requests or matchmaking requests (available on request)
Which UTM tags PartnerPage saves
UTM tags are parameters you add to the end of a link. PartnerPage saves every parameter that starts with utm_, including the five standard ones:
Tag | What it describes | Example |
| Where the visitor came from |
|
| The type of channel |
|
| The campaign or promotion |
|
| The paid search keyword |
|
| Which version of the link or ad |
|
An example link: https://partners.example.com/?utm_source=newsletter&utm_medium=email&utm_campaign=q4-partner-launch
Tags work on any page of your directory, including a partner's profile page.
How PartnerPage captures UTM tags
When a visitor opens your directory from a link with UTM tags, PartnerPage keeps the tags while the visitor browses in the same browser tab. If the visitor then sends a contact request from a partner's profile or a matchmaking request, PartnerPage saves the tags with that request.
Closing the tab ends it: the tags are lost when the visitor closes the tab or opens your directory in a new tab.
The last tagged link wins: if the visitor arrives again in the same tab through another tagged link, the new tags replace the old ones.
Matchmaking carries over: when you assign a matchmaking request to partners, each contact request created from it keeps the matchmaking request's tags.
Applications and deal registrations: partner applications and deal registrations don't keep UTM tags.
See UTM tags in an export
In your directory's sidebar, open Contact requests or Matchmaking requests and export the list. The CSV file has a column for each standard tag: utm_source, utm_medium, utm_campaign, utm_term and utm_content. A cell is empty when the request had no tag. Other utm_ tags are saved but not exported: read them through webhooks or the API. See Export partners, applications and reviews.
The request pages in the dashboard and Reporting don't show UTM tags. Use the export to count requests by campaign.
Receive UTM tags in webhooks and the API
For developers: in webhooks, the tags are in a utm_query_params object, for example {"utm_source": "newsletter", "utm_medium": "email"}, or null when the request had none. The API returns the same data as utmQueryParams, with camelCase keys such as utmSource and utmMedium.
Directory webhooks: the
contact_request_created,contact_request_updated,matchmaking_request_createdandmatchmaking_request_updatedevents includeutm_query_params. See Set up webhooks for your directory.Lead webhook for partners: partners who send their contact requests to their own tools with the Lead webhook also receive
utm_query_params. See Send contact requests to your own tools with the Lead webhook.API: contact requests and matchmaking requests you read through the PartnerPage API include
utmQueryParams. When your own systems create a contact request or a matchmaking request through the API, you can send the tags with it. Endpoints and fields are in the API reference at https://docs.partnerpage.io.
Common questions
Why is the UTM column empty for a request?
The UTM column is empty when the visitor didn't arrive through a tagged link, closed the tab before sending the form, or opened your directory in a new tab. A contact request you reassign or duplicate also starts without tags: the original request keeps them.
Can I see UTM tags for partner applications?
No. Partner applications and deal registrations don't keep UTM tags. Only contact requests and matchmaking requests do.