Google AdWords: Event and parameter data sent through your retargeting pixel

Feature.fm sends retargeting data to your Google AdWords account through a single custom event, which allows you to create custom audiences and run custom conversion campaigns based on the actions fans take on your Feature.fm landing pages. This custom event includes a set of parameters that correspond to each action a fan takes. Read more about these parameters here. 

The event name that will be sent to your retargeting AdWords dashboard is called 'FeatureFM.'

First, you will need to make sure you've added your retargeting pixel - either to your Default Link Settings, or on the individual smart link, or both. For guidance on how to create a Google Ads pixel and where to add to your Feature.fm account, refer to these articles:

Getting your Facebook & Google Retargeting Pixels from pixel code

Where to enter your Retargeting Pixels in Feature.fm

Once you've got your pixel installed correctly, the 'FeatureFM' event will be ready to fire once someone visits the landing page.

What data gets sent through the 'FeatureFM' event?

There are 4 actions that fans can take on a smart link that will fire the retargeting pixel and trigger the 'FeatureFM' event to send. The 'FeatureFM' event will include one of the following parameters, each called [action] with one of the below values:

With each retargeting action event, the 'FeatureFM' event will fire and we also send detailed event parameters so you can further refine your audience segments based on action taken, genres, artists, preferred music services and more. 

Below are examples of the parameters that are always sent when your retargeting pixel fires.

You can learn more about the parameter definitions and see a more complete list of parameter values in this article.

Each action event may also include parameters that are specific to the action type. You can see these unique parameters and values below:

The 'pageview' action is sent when a fan clicks on one of your and visits your landing page.

Below is an example of the parameters that are included with the 'pageview' action:

The 'musicservice' action is sent when a fan clicks to a music service or store from your landing page.

Below are the parameters that are included with the 'musicservice' action:

The 'preview' action is sent when a fan clicks the preview on your landing page.

Below are the parameters that are included with the 'preview' action:

The 'presave' action is sent when a fan clicks to presave from a supported Pre-Save store.

Below are the parameters that are included with the 'presave' action:

You can learn more about how to set up your custom audiences with Feature.fm's events here.