Skip to main content

How to customize UTM tracking in WAX

WAX automatically adds UTM parameters to every link sent in your campaigns and automations. This lets you track the performance of your WhatsApp actions precisely in your analytics tools, with no manual setup on your side.

Good news: you can customize this behavior to fit your CRM needs, directly from the platform settings.

What you need to know

Before you set anything up, keep these 3 rules in mind:

  1. WAX never replaces a parameter already in a link. If a link already contains a UTM (for example because you added it manually), WAX only adds what's missing and never touches what's there.

  2. An empty field = a disabled parameter. If you empty the utm_medium field, for example, this parameter simply won't be added to your links anymore.

  3. utm_campaign has a dynamic default value. By default, this field isn't fixed text: it's a token that automatically inserts the name of your campaign or flow. Handy, so you don't have to rename this parameter for every send.

Where to set your UTMs

📍 Settings → Attribution → UTM tracking

All UTM tracking settings are here .

Step by step

1. Open the settings

Go to Settings → Attribution → UTM tracking

2. Turn automatic UTMs on or off

Use the Automatically add UTM parameters toggle to turn the feature on or off globally.

3. Set your UTM fields

Fill in the values to fit your reporting needs:

Parameter

Default value

What it's for

utm_source

wax

Identifies the traffic source (here, the WAX platform)

utm_medium

whatsapp

Identifies the channel used (WhatsApp)

utm_campaign

Dynamic token = name of the campaign/flow

Identifies the specific marketing action behind the click

💡 CRM tip: if you track performance by channel in a tool like GA4, keep a UTM naming scheme consistent with your other channels (email, SMS, etc.) to make cross-channel comparisons easier.

4. Save your changes

Click Save.

⚠️ Changes apply immediately to all future sends: campaigns and automations. Links sent before the change are not affected.

Did this answer your question?