Reach represents the number of unique visitors exposed to your content over a specified time period. Reach differs from impressions, which includes multiple views by the same visitor.
You can't sum Reach data. For example, when analyzing reach in 7-day increments, a user can view your content twice in one week and twice the following week. Each week, the user is counted as a single user, but you can’t add them up because the sum no longer conveys a unique user for the specified time period. Total Reach isn’t a sum of reach calculated in shorter increments. Instead, total reach represents the reach of a page or an individual piece of content in a specific time-frame that includes various types of reach. Cookie- level data is not available when ingesting specific data into Intelligence. To ensure that your report displays the correct data, aggregate your data at the granularity that you want the report to reflect.
- Reporting Reach at Multiple Entity Levels
To see reach at multiple levels or different frequencies in Intelligence for example, daily, weekly, or monthly, you create multiple APIs or TotalConnect data streams, differing the entity dimensions or date range per data stream. - Processing Historical Data for Reach Data Streams
When manually processing data streams, Marketing Cloud Intelligence doesn’t consider the sliding window. Data needs to be processed in one month increments to ensure integrity of reach data is not compromised. You have to be conscious of how your regular retrieval is set up - to ensure that the newly loaded historical data and what you will regularly receive in the data stream are even comparable. - Field Mapping for Reach Data Streams
It’s important to map the day and reach fields correctly in a reach data stream. The mapping can vary depending on the granularity that you’re setting up. Only map the required fields.