Introduction
To make it as easy as possible using CamBuildr within your performance campaign, we added our own tagging scheme, that makes it easy to optimize your campaign and targeting.
You can embed 4 different types of tagging into CamBuildr:
Google Tag Manager
Google Analytics
FB Pixel
Custom HTML (for Matomo, etc.)
Our preference goes to Google Tag Manager, as it allows you to simple embed all the custom actions to be at your use. See Import CamBuildr Actions into GTM for more details on how to use our template for Google Tag Manager.
As a plus, we also defined to general triggers in Google Tag Manager, which indicate a user starts interacting with your campaign and a user signing up with your campaign. That makes it easier for you to do effective retargeting:
List of Actions
Here is a list of all the custom actions being sent to your configuered GTM, Analytics and FB. The Lead checkmark indicates, if there is also a Facebook lead event sent on this occasion.
Landingpages
Action Name | Triggered when | Lead |
| User starts filling out a form |
|
| User submits the form | ✅ |
Surveys
Action Name | Triggered when | Lead |
| User starts interacting on a survey |
|
| User selects an answer |
|
| User starts the Verification Process in Verified Voting |
|
| User signs up after survey | ✅ |
Variable Name | Value |
| Answer-Text or Sentiment Value |
User Stories
Action Name | Triggered when | Lead |
| User submits a picture or starts filling out the form |
|
| User uploaded a picture |
|
| User entered the person data |
|
| User entered a statement |
|
| User submitted the story | ✅ |
Variable Name | Value |
| Category Name where the story was submitted to |
User Stories Voting
Action Name | Triggered when | Lead |
| User swipes on the first card |
|
| For every YES-Voting |
|
| User signs up with email | ✅ |
Variable Name | Value |
| The Content-Id the user answered with YES |
Public Supporters
Action Name | Triggered when | Lead |
| User submits a picture or starts filling out the form |
|
| User uploaded a picture |
|
| User entered the person data |
|
| User entered a statement |
|
| User submitted the entry | ✅ |
User Events
Action Name | Triggered when | Lead |
| User starts creating a new event |
|
| User submitted a new event | ✅ |
| User starts participating in an event |
|
| User participates in an event | ✅ |
Variable Name | Value |
| The category of the event |
| The id of the event |
User Campaigns
Action Name | Triggered when | Lead |
| User starts creating a new campaign |
|
| User submitted a new campaign | ✅ |
| User starts participating in a campaign |
|
| User participates in a campaign | ✅ |
Variable Name | Value |
| The id of the campaign |
Donations
Action Name | Triggered when | Lead |
| User starts the interaction and selects the amount |
|
| User starts the payment |
|
| User donated | ✅ |
Variable Name | Value |
| The amount of the donation |
Voting App
Action Name | Triggered when | Lead |
| User starts the interaction |
|
| User submits a vote | ✅ |
AB Test Target Audiences
To be able to separate between different audiences in the AB-Tests, we provide you with a variable CamBuildr - AB Test Variant
which contains the page title and the variant name the person is viewing. Also there is a trigger CamBuildr - AB Variant Found
that is triggered, if a page with an ab variant is loaded.
Import CamBuildr Actions into GTM
You can import our template right into Google Tag Manager and are ready to use our predefined triggers and variables.
Current Version 5 - October 29th 2024