Skip to main content

​
Context

In the Bucket integration, the standard UTM fields (utm_source, utm_medium, utm_campaign, utm_content) are usually already in use by the client’s GA4 and must not be changed. The only free field for Nemu’s attribution is utm_term. That’s why all attribution data (source, campaign, ad set and creative) is packed into a single utm_term, which the client’s GA4 captures and passes on to Nemu.

​
How the configuration works

Each channel (Meta, Google, TikTok) sends the packed utm_term in the destination URL. All of Nemu’s attribution data (source, campaign, ad set and creative) is concatenated into this single field, which the client’s GA4 captures and sends back to Nemu, which then unpacks it and rebuilds each piece of information.
The utm_source, utm_medium, utm_campaign and utm_content fields stay as they are today, unchanged. They belong to the client’s GA4 and must not be touched.

​
Where to configure

All of this configuration is done inside each platform’s ads manager, in the URL parameters / tracking field. There are no changes to the client’s website or checkout: the parameters are appended to the destination URL by the ads platform itself.

​
Parameters per platform

On each platform, paste the corresponding utm_term parameter:

​
Meta

Meta:

​
Google

Google:

​
TikTok

TikTok:

​
Field map (reference)

​
Implementation notes

A single field. All of Nemu’s attribution is concatenated into utm_term. This is the field GA4 captures and passes on to Nemu, so it must be filled in on every destination URL.
Don’t change the other UTMs. utm_source, utm_medium, utm_campaign and utm_content stay as they’re already configured in the client’s GA4.