|Click Tracking Pixel||Can a browser handle large (character-based) click tracking pixel URLs?||Yes, although the click tracking URLs could be quite long, this will almost never cause issues. Under normal conditions, the macros are much longer than the actual values once populated. Moreover, modern browsers are capable of handling URLs which are much longer than the average click tracking URLs. Nevertheless, we do advise to test the click tracking URLs before putting it in production.|
|Click Tracking Pixel||Can the click tracking pixel be tested to review whether it is working correctly? there a way to check if the click URL of a Mapp DMP Pixel is working correctly?||You can check if the pixel is properly implemented by opening the click tracking pixel URL in your browser. If the pixel is implemented correctly, you should then be redirected to the correct landing page. This work in all instances, even when you customized the click tracking pixel.|
|Click Tracking Pixel||Can the process of adding impression tracking pixels to creatives be automated?||The process of automatically implementing impression tracking pixels onto new creatives is currently only applicable to certain the AppNexus (DSP) integration. Please contact your Account Manager in case you want to explore other possibilities.|
|Can you create Impressions or Click Tracking Pixels for platforms that are not available from the dropdown in the 'Export' tab (step 3) of Data Collection?||Yes, new platforms can be added to this list. This normally takes up to 24 hours and can be prioritized in case of urgent needs. Please file a support ticket or contact your Account Manager in case you have such a request.|
|Functionality||What is the 'Data Collection' feature?||Our DMP includes an easy to use interface to create on-site pixels and/or impression and click trackers. The on-site pixels need to be placed directly on the website to gather 1st party data. This is just one line of code that can be implemented in the header or body of a website. The same code can be used for each and every page and no additional customization is needed. The impression and Click trackers can be exported for various marketing and advertising platforms in order to collect ad serving data. In addition there are several options to enrich the data collected through our on-site pixel or through the impression and click trackers. Note that first party data from other platforms (proprietary or in-house) follow the a same procedure as for integrations.|
|Functionality||What standard data is being collected automatically by means of the Mapp Acquirepixels?||An overview of our log format containing all default data fields can be found elsewhere in the wiki. It will provide more details as well as examples that are relevant for the various pixel events.|
|Functionality||When does the data becomes available in the DMP once I implemented a pixel?||From the moment our DMP pixel servers are being called it takes up to several minutes before it is permanently stored in our cluster. From there the data will be derived into the relevant databases that serves as the basis for almost all DMP features. It therefore only takes 10 to 15 minutes before the data becomes available for audience building purposes. Please note that the counters in the Real-Time Dashboad does not deal with any latencies.|
|Functionality||Is it mandatory to collect the IP addresses of users by default?||No, this is not mandatory. In case you not wish to use the IP addresses or may not want to collect them you can reach out to your Account Manager. There are several options to be compliant or to restrict the collection of IP addresses out of privacy concerns such as hashing or truncating.|
|Functionality||What is the purpose of collecting the IP addresses of users?||The IP address will be collected automatically and being used for several purposes. First of all, the IP could be used as an alternative user or common identifier to connect data sources or systems. Secondly, the geographical elements of our data feed will be retrieved by a geo-IP look-up based on an external database. Lastly, the IP addresses will also be used to automatically prevent fraud.|
|Functionality||What is the difference between the referer_url and the event_referer_url?||The referer_url is present in the 'Request Header' section of the browser console and represents the referer of the pixel itself. In case a user enters a page on which the pixel is active and being loaded for the first time this referer_url is always similar to the actual event_url. When you then visit the 'next page' it will be the url of the first page visit where the pixel was loaded. Consider this as the internal pixel referer_url. The event_referer_url is present in the 'Query String Parameters' section of the browser console. This is the referer_url as represent in the 'Query String Parameters' section. As an example you could imagine that a user has entered the page on which the pixel is active as a result of clicking on a google search entry and can therefore be seen as the cross-domain referer_url.|
|Functionality||Will the event_referer_url always be transparent?||No, unfortunately not. There are instances where the DMP pixel is not able to populate the event_referer_url (cross-domain) due to a couple of reasons. First of all, the event_referer_url could be a secure page. Secondly, the user could have restrict the DMP pixel to capture the event_referer_url as part of the browser settings. Lastly, the user could have installed plugins like ghostery which makes it impossible for the DMP pixel to capture the event_referer_url.|
|Functionality||What is the level of domain transparency relevant to the Mapp DMP pixels?||The DMP stores all domains that we have access to, independent on the type of pixel collector. So there is no such thing as an 'undisclosed' domain. However, in some cases we are unable to detect the domain ourselves as they are not provided, for example when the creative has been served in an (double) iframe.|
|Functionality||After how much time will the data being collected becomes unavailable for audience creation?||Customer’s raw data will be stored for one (1) year by default after which it will be stored in aggregated form for a maximum period of five (5) years. The cookie lifetime is set to two years by default. So our clients will still be able to create an audience based on the available data events, even after several months, although the maximum look back window within the Custom Audience builder is currently set at 30 days. Please note that the expiry data of an execution platform can differ from the numbers above.|
Which possibilities do you have to check the correct placement of pixels and containers?
An important step of the onboarding procedure is to check whether the pixel is implemented correctly and if the data is being collected properly. In order to do so, the DMP includes a feature to verify the DMP pixel loads in a user-friendly way and without the need for developer skills. A ‘Pixel Activity Monitor’ can be enabled as an On-Site pixel module and serves as a tool to verify, if the DMP pixel is active on the website. It will pop-up as a floating and draggable element in your browser and shows all data events that are initiated by the implemented pixel script. This also includes interaction events like ‘Time on Page’, ‘Page Scroll’, and ‘Form Interactions’ that are originating from the default pixel modules.
|Implementation||How does the impression tracking pixel needs to be implemented?||The impression tracking pixel as exported from the Mapp DMP interface must be implemented on a creative or ad unit level in the execution platform. Therefore we suggest to consult the documentation available from the execution platform which normally contains one or more entries about 'adding 3rd party impression tracking pixels'.|
|Implementation||How does the click tracking pixel needs to be implemented?||The click tracking pixel as exported from the Mapp DMP interface must be implemented on a creative or ad unit level in the execution platform. As part of the implementation you need to make sure that the relevant 'Landing Page URL' will be added or dynamically populated after the '&out=' parameter. We suggest to consult the documentation available from the execution platform which normally contains one or more entries about 'adding 3rd party click tracking pixels'.|
|Implementation||Should the on-site pixel code be added to every page on the website or just to certain pages?||The pixel code should be placed on every page. However, if you feel a particular page is too sensitive, you can leave out the pixel code.|
|Implementation||Can two on-site DMP pixels be implemented on a single website?||Yes, the tags are isolated meaning that multiple tags can be implemented on a single page without conflicting each other. Moreover, the pixels will fire asynchronously so it should never be able to affect loading times or resulting in errors visible for the visitors.|
|Implementation||Can your on-site pixel be placed into a container tag?||Yes, our pixel can be deployed through all tag managers. This includes but is not limited to Google Tag Manager, Qubit, and Tealium.|
|Implementation||Can the pixel be implemented into an iFrame?||Yes that is possible, but we strongly advise to not do this. If you implement the pixel in an iframe it will only measure the actual loads and just a couple of other variables. Note that the event_url and/or referer_url in this case will also reference to the url of the iFrame.|
|Implementation||What are the limitations of an image pixel in terms of data collection capabilities?||Image pixels cannot execute code so image pixels are not capable of collecting any interactions. |
|Impression Tracking Pixel||To what extent can I customize the Impression Trackers?|
The impression trackers pixels can be customized to a large extent by means of predefined parameters as part of our log format. You're able to add and delete variables. However, some variables are required. The impression tracking pixels will not work without the following variables:
- Member ID (m)
- Pixel ID (id)
- Creative ID (cid)
Impression Tracking Pixel
|Can you create Impressions Tracking Pixels for platforms that are not available from the dropdown in the 'Export' tab (step 3) of Data Collection?||Yes, new platforms can be added to this list. This normally takes up to 24 hours and can be prioritized in case of urgent needs. Please file a support ticket or contact your Account Manager in case you have such a request.|
|Mobile||What are the limitations of the Mapp on-site pixel on mobile?||The pixel works just fine on a mobile browser. The in-app implementation is more complex as this requires an SDK or specific customization of the regular on-site pixel. Nevertheless we already have clients that successfully customized the on-site pixel in order to capture client specific data based on user behaviour in their mobile app.|
|Mobile||Do you have a mobile Software Development Kit (SDK)?||We have an alpha version of the mobile SDK for iOS and Android which cannot be exposed to clients (yet). However, the Mapp team is always available to assist in collecting any data from mobile apps and can provide you of examples. Please note that a much deeper and more sophisticated integration with the mobile capabilities of DMC is on the roadmap and will be worked on accordingly.|
|Mobile||Do you need an mobile Software Development Kit (SDK) to collect in-app data?||No, there is an alternative way to capture specific mobile in-app data by means of customizing the regular on-site pixel. Mapp provides clear guidelines which can be found in this document.|
|Mobile||Describe your technology’s awareness/approach to understanding and impacting mobility (both customers engaging via mobile- searching, calling, in-app, email, etc. and how can the company activate via mobile - for example, ads, apps, on location, call center, etc.).||The Mapp Data Management Platform is part of Mapp’s Digital Marketing Center (DMC). Within DMC we have a mobile app offering which can be used to collect and execute data in apps.|
|On-Site Pixel||What is the difference between the interaction tracking modules 'Webform Interactions' and 'Form Values'?||With the 'Webform Interactions' module enabled a data event will be collected at any time a user has interacted with any webform on the website, including search bars. It basically just tracks interactions of the type webform focus, webform click or webform input but ignores the actual value entered in case of the latter. With the 'Form Values' module enabled the DMP does actually collect this value being entered into a webform field. Please note that these Form Values are being stored unhashed by default which may result in the collection of PII. Mapp is not responsible for this so in case a certain value needs to be hashed you can reach out to your account manager before enabling the 'Form Values' module.|
|On-Site Pixel||What is the difference between an on-site Segment and an on-site Conversion?||Segment and conversions are industry-standard labels for targetable enitites (terminology).The only difference from a technical perspective is that you can apply deduplication settings on a conversion level within the Mapp DMP. For the rest they both represent a conglomeration of unique User IDs (cookies) that will be added to the entity when the on-site user interactions meets the condition(s) that have been configured for this segment or conversion. Typically a conversion serves as a recognizable label of valuable user interactions in an e-commerce environment such as a purchase event, a subscribe event, or a download event.|
|Performance||Does the Mapp DMP Pixel impact performance of the website?||No, all our pixels load asynchronously. Because of this our pixels do not affect the loading time of a website. The asynchronous loading time should be less than one second under normal conditions. You can always inspect the loading time in the console of your web browser.|
|Performance||In case the Mapp servers are not accessible or slow to respons for any reason, what would be the expected impact on the actual website?||Given the fact that all of the DMP pixels are loading asynchronously, they should never impact a websites' loading time or user experience. This should even not happen in the very unlikely scenario of when the DMP pixels takes minutes to load or is unresponsive.|
|Tag Manager||Do you have a self service tag manager?||Yes, the 'Configure On-Site' section as part of the data collection workflow can be considered as an integrated and self-service tag management solution.|
|Tag Manager||Does the Mapp DMP offer piggyback possibilities for external pixels?||Yes, this can be managed from within the 'Configure On-Site' section as part of the Data Collection workflow. When creating a segment or conversion it allow you to populate external pixels as an optional configuration. All type of pixels (e.g. image url, script, etc.) are supported and can be added on the flight. After hitting the 'Save' button the on-site pixel will be automatically redeployed to take all changes into consideration. Therefore, the DMP on-site pixel functions as a container tag but can also be incorporated into an external container tag (vice versa).|
|Tag Manager||Can we track frequency and/or recency aspects on a user level within the DMP?||Yes, by default we track various kinds of user interactions on a webpage where the on-site DMP pixel is implemented and activated. You can further specify frequency and recency metrics within the 'Configure On-Site' section by creating segment or conversions and apply deduplication rules.|
Do you have functionality that provides custom naming conventions on top of standard tag IDs for better handling of complex client and cross country setups?
Yes, apart from the standard naming convention of pixel and attributes, the DMP supports to use custom labels, taxonomies or hierarchies. Therefore, it can be fully implemented according to our client’s needs in terms of structure and setup.
|Taxonomy||Is it possible to create our own taxonomy/hierarchy for data points?||Yes, we have APIs available and could provide an user-friendly interface that enables you to classify content or create your own taxonomy based on the available data points. and an interface that should enable you to classify content. Please contact your Account Manager in case you want to further explore the possibilities or have any additional questions.|
Can I use user-defined variables?
Because every website has its own content and structure it is important to customize the DMP On-Site Pixel according to your client needs. The Custom Data feature enables you to capture relevant elements from a specific website/webpage that are available from the source code or even from user generated content and send it to the DMP in real-time. This enables you to store highly relevant data attributes that can be used to create advanced Custom Audiences.