February 20, 2018
Audience Manager does not collect the data itself, it relies on external sources. Here’s a quick overview of all available data sources:
Audience Manager adds it’s own Forms tracker to Tag Manager. It allows you to gather all information passed in forms on your website.
Enabling forms tracking
In order to start tracking data from forms, you need to add and publish an Audience Manager tag in the Tag Manager:
Go to Tag Manager “Tags” section
Create new tag
From the list of tag types, select: “Piwik PRO Audience Manager”
Click OK and it’s set. Of course to push it live, the tag has to be published.
Forms tracking behavior
Once the tag is published, Audience Manager will be tracking all forms present on the website.
Important rules and behavior of form tracking:
Data is saved to Audience Manager only when the form is submitted
Password inputs are not saved
Credit card data is not saved – we’re doing our best to guess that detected form collects credit card information and ignore it but in rare cases when the form is some sort of a custom setup, our patterns could be mismatched and credit card data will be captured. It’s recommended to test that kind of forms after enabling forms tracking to make sure that it’s ignored.
Data from forms is saved as custom attributes in the profile. The name of an attribute is taken from the name of input field of the form – .e. if the form has following input fields with names defined in HTML attributes: name, gender, email_address, they will be saved in the profile under attributes with exactly the same names.
Saving email as one of profile IDs – Audience Manager tests form values against patterns matching the email address. In case there is a match, regardless of what was the name of the input field the email address will be saved as a one of profile IDs under email attribute. Based on the example form described in the above point there will be 2 attributes saved:
email – special attribute maintained by Audience Manager as one of profile IDs
email_address – attribute saved directly from the submitted form
If the attribute already exists in the profile, it will be replaced by the latest value sent to Audience Manager.
It is also possible to manually exclude entire form or only particular form inputs from tracking. This might be useful if you collect some sensitive data which you don’t want to be stored in Audience Manager. To set it up go to the tag configuration in Tag Manager:
Go to the forms tracking tag
Select “Exclude data from selected forms”
Enter form ID (from id attribute in HTML)
If you want to block entire form save this configuration
If you want to block only one or few input fields from the form, select “Exclude only specific fields” and provide fields names (from name attribute in HTML element)
You can add as many forms or fields as you need.
Generic Analytics Data
Some analytics data is tracked automatically once the integration with Analytics is enabled.
analytics visitor IDs,
browser and device data,
user IDs (if used).
Audience Manager’s integration with Analytics should be enabled by an administrator – usually during the technical implementation phase.
Custom Variables & Dimensions
Both Custom Variables and Custom Dimensions tracked in Analytics are automatically mapped to custom profile attributes (the same pool of attributes that can be tracked from forms or SDK).
Rules are fairly straightforward:
Name of the variable/dimension is normalized to lowercase ASCII (with underscores). For dimensions, the attribute name is the name of the dimension from the time the value was tracked (in other words, changing the name of a dimension in Analytics will not change any tracked attributes retroactively).
Only the most recent value of each attribute is stored (values are overwritten across all “custom” data sources).
Custom Events are also mapped to custom profile attributes, but unlike Variables and Dimensions, this does not happen automatically.
In order to setup Custom Event mapping:
Go to Attributes tab
Select the attribute where one of the Custom Event fields should be stored and click on the gear icon. If the attribute does not yet exist, use “Create new attribute” button to add it
Click on “New event mapping”
Setup filtering by selecting any subset of the Category, Name and Action fields and configuring the operator and valueOnly Custom Events matching these rules will be mapped
Select the attribute value from the “Mapped event attribute” dropdownNote that the attribute value will always become a string, even when using Value field
Click on the Save button
Once saved, Custom Events that match specified filtering rules will have the specified field stored as the selected attribute.
Each goal tracked in Analytics is automatically saved in profile as “event” data type.
For each goal separately, we store:
the timestamp of the most recent goal conversion, and
the total number of conversions.
Goals data is stored using goal IDs, so changing goal name in Analytics does not impact profiles or audiences in any way (i.e. it’s still the same goal).
Filters related to goals are available in the “Events” tab in the audience builder.
Similar to goals, ecommerce conversions tracked in Analytics automatically store some data in profiles, namely:
total number of ecommerce conversions,
total revenue from all ecommerce conversions,
revenue from the most recent ecommerce conversion,
timestamp of the most recent ecommerce conversion.
We do not store abandoned carts and any content of the specific ecommerce orders. It’s also not possible to filter revenue or conversion count by date range (it’s always “all time” or the most recent event).
Filters related to ecommerce conversions are available in the “Events” tab in the audience builder.
Additionally, to the data collected from Analytics and from the forms, you can import data from third-party platforms. For example, you can use data sources from your CRM to enrich profiles.
Importing the CSV file consists of following steps:
Select the file to import, mind that CSV file must meet some requirements: First row is a header that contains columns names; Supported separators: Comma sign (,), Semicolon (;), Tab; Data must be written in UTF-8 encoding.
Choose identifier type and the column which stores identifiers in CSV file – the identifier is used to match imported user data to profiles stored in Audience Manager.
Choose columns to import.
Map columns to attributes in profiles – enter the attribute name for each selected column. In case the attribute exists, it will be overwritten by the value imported from the CSV file, otherwise, new attribute will be created.
Piwik PRO has an SDK library for Android and iOS, that integrates your application with Piwik PRO Analytics in a convenient manner. It serves as a replacement for web script tag in mobile devices.
Using SDK you can:
track custom profile attributes
track ecommerce events
track custom variables and dimensions
Integration with goals, ecommerce events, custom variables and dimensions work in the same way as web integration described above.
When tracking custom attributes via SDK, the following fields are saved:
Device ID – on iOS only when an app is approved in App Store to read it
Visitor ID – autogenerated by the SDK, it’s not changing as long as user reinstalls the app
User ID – if provided
Email – if provided
any key-value pair sent to Audience Manager which is saved as a profile attribute and its value
Public API’s Documentation is available under http://am.devtools.piwik.pro
Retrieve list of audiences the profile belongs to.
Check if given profile belongs to given audience.
Retrieve public attributes for given profile. Public attributes are configured in the web ui.
Track custom attributes for a given profile.
PublicAPI is suited for platforms, where no SDK is available or for server-to-server integrations. by using public API, it’s possible to: