Note: This topic is currently meant for Full Circle employees only. At no point should you be editing the existing Aggregate Field Mappings. This information is being provided for informational purposes only. Its configuration may only be necessary in the following situation:
- A custom project where a customer is requesting integration from a currently-unsupported data source, into DST Pro
Assumptions
Before beginning this configuration phase, the following assumptions should hold:
- The person configuring this should have an understanding of Salesforce's custom metadata type feature,
- Any editing of existing Aggregate Field Mappings is done with the knowledge, oversight, and consent of a Full Circle R&D point of contact
Understanding the Aggregate Field Mapping Custom Metadata Type
Digital Source Tracker Pro comes packaged with a custom metadata type called the Aggregate Field Mapping. Digital Source Tracker Pro's back-end aggregate engine uses Aggregate Field Mappings to populate information into Aggregate Database Entry records.
Several Aggregate Field Mappings are provided that are pre-configured to flow data from the following data sources into the Aggregate Database Entry object:
- Google Analytics
- Digital Source Tracker Standard (this is pulling in information that DST Standard stores in AWS)
- Funnel Metrics (within Response Management)
Some of the data sources push data into the same Aggregate Database Entry field. For example, the Campaign field on the Aggregate Database Entry record may house the utm-campaign parameter attribute from a DST Standard data source, then house the name of a campaign as tracked in Google Analytics. Make sure you review the topic on Aggregate Database Entry Fields and Descriptions to understand what each data source populates into which field.
Aggregate Field Mapping Fields and Descriptions
| Term | Definition |
|---|---|
| Label | The user-friendly name of the Aggregate Field MappingP |
| Aggregate Field Mapping Name | The API name of the Aggregate Field Mapping |
| Aggregate Entry Reference | Lookup to the Aggregate Database Entry object. This is a field required by Salesforce when working with custom metadata types. Do not edit this. |
| Aggregate Entry Field | The field on the Aggregate Database Entry object that will be populated with information based on the data source. |
| Datasource Tag | Custom value that describes the data source. |
| Datasource Field | This is the API name of a field from the data source, that will be populating the Aggregate Entry Field. |
| Schema Name | On the Aggregate Database Entry object, this is reflected as the "Data Source". |
| Self Configured Schema | Liz needs help with this definition. Current Help text is unclear: "When true, this entry represents a schema whose fields mappings are auto-configured or self-configured rather than relying on this custom metadata type." (LK: what other configuration options are there after self-configuration & auto-configuration....manual?? What is a business context for checking this box?) |
| Self Configured Schema Entries | If a schema is self-configured, this field determines how many Aggregate Database Entry records are created in a day, for this schema. Liz needs help with this definition |
| Protected Component | Liz needs help with this definition |
| Namespace Prefix | Liz needs help with this definition |
Comments
0 comments
Please sign in to leave a comment.