Re: Reporting on Trigger token data

Evelina_F
Level 2

Reporting on Trigger token data

Hello,

We are currently using the {{trigger.web page}} token to pass the URL from form fills into email alerts. We have received a request asking for the data to be visible in the campaign smart list view or a report so that URLs can be tracked and exported. The goal is to use this data to help us confirm which web pages have the highest intent and determine what content generates the most demo requests and interest, for which we currently have no baseline. To achieve this, we propose the following:

We want to capture the {{trigger.web page}} token value and store it in a custom field that we can then pull into the campaign smart list view. This involves creating Marketo-only fields that we can stamp with the trigger value {{trigger.web page}}. Once these values are stamped, we can access them using the token for that field in subsequent campaign flows. As the custom field will be used in multiple campaigns, our concern is that if contacts fill out various forms on multiple pages, the values will be overridden each time, leading to inaccurate data. To address this, we would write the contacts to a static list based on specific criteria.

This option would take time and resources, which we currently do not have, we are open to alternative ways to achieve our goal. If anyone has any suggestions, we would greatly appreciate it.

Thank you!

2 REPLIES 2
SanfordWhiteman
Level 10 - Community Moderator

Re: Reporting on Trigger token data

You should use a Program Member Custom Field, not a Person Field.

 

PMCFs allow you to store different {{trigger.web page}} values for the same person simultaneously.

 

Also note {{trigger.referrer}} is more complete than {{trigger.web page}}.

Evelina_F
Level 2

Re: Reporting on Trigger token data

Thank you @SanfordWhiteman