Campaign ID - Example
Overview
As described here, the Campaign ID (or "Camp ID") is a unique, system-generated identifier assigned to every Campaign when the Campaign is launched (or when a Web Page is published).
If your Campaign utilizes the Cells and Splits feature (which allows marketers to divide their Campaign audience into smaller segments, or cells) a unique Campaign ID is assigned to each unique cell created in the Campaign. This means that there is no singular Campaign ID value that ties all cells together for the Campaign in question. This is important to understand if you're attempting to utilize the Campaign ID value for reporting and/or aggregation purposes at a “global” campaign level, especially if you're consuming this data outside of Engage+ (such as in your internal systems, or in a third party system).
As an example, let’s say a user creates a Campaign with four cells, all split by a Filter. One of those splits is further split by Gender, and each of those Gender splits is further split by 50/50 percentages. Essentially we now have four levels in this Campaign.
The following table represents the "cell tree" for this Campaign. The red highlighting is used to indicate "sending cells," which are described below in more detail.
|
Camp ID |
Cell Code |
Filter |
Split type |
Split Field Name |
Split Value |
|
1 |
Code1 |
Domain Audience |
|
|
|
|
2 |
Code2 |
gmail emails |
filter |
|
Segment 1 |
|
3 |
Code3 |
yahoo emails |
filter |
|
Segment 2 |
|
4 |
Code4 |
aol emails |
filter |
|
Segment 3 |
|
5 |
Code5 |
msn emails |
filter |
|
Segment 4 |
|
6 |
Code5_M |
msn emails |
field |
gender |
M |
|
7 |
Code5_M_%50 |
msn emails |
percentage |
50 |
|
|
8 |
Code5_M_%50 |
msn emails |
percentage |
50 |
|
|
9 |
Code5_F |
msn emails |
field |
gender |
F |
|
10 |
Code5_F_%50 |
msn emails |
percentage |
|
50 |
|
11 |
Code5_F_%50 |
msn emails |
percentage |
|
50 |
In the above cell tree, you'll notice that each Cell within the Campaign has been assigned its own unique Campaign ID value. For instance, the "parent” Cell (i.e. [Camp_ID] = 1), which has four children ([Camp_ID] values of 2, 3, 4 and 5). One of those children ([Camp_ID] = 5) has two children of its own (i.e. genders of 'M' & 'F', or [Camp_ID] values of 6 and 9), where each of them has two children of their own (i.e. 50% splits, or [Camp_ID] values 7,8, 10 and 11).
Sending Cells vs. Non-sending Cells
Standard export activities will export data for all cells, regardless of whether or not a given cell exists with sending activity tied to it or not.
Sending cells are highlighted in red in the cell tree above. A sending cell refers to a cell that is actually utilized to send messages. Other cells (called "non-sending cells) are used merely to further segment data into additional cells. Non-sending cells are essentially "folders" containing additional sub-cells, but don't actually send any data to consumers.
For example, the “parent” Cell (i.e. [Camp_ID] = 1) would NOT actually have any sending activity as it is merely a “parent” to other cells from which send activity is actually generated. The same can be said for the cells tagged with [Camp_ID] values of 5, 6, and 9. Messages are NOT deployed from these cells. However, these cells are necessary as an organizational tool, in order to properly segment the universe of data into the user’s desired sending cells.
In the example above, we have the initial qualifying universe of data (i.e. [Camp_ID] = 1), which is segmented into four groups of email domains, where one of those domains, ‘msn emails,’ is a non-sending cell that is further segmented by Gender (i.e. [Camp_ID] values of 6 and 9), which are also non-sending cells, to get to the desired sending cells that will actually have sending activity tied to them.
In the above scenario, there is no singular Campaign ID that would give you a "global" view of the entire Campaign activity. If you attempted to use the parent-level Campaign ID ([Camp_ID] = 1), you wouldn't see any data, because this Campaign ID is not a "sending cell."
If you need to consume Campaign data in your internal systems, or in a third-party system, for the purpose of aggregating data, or reporting on a given Campaign, you'll need to use something other than Campaign ID as the unique Campaign identifier. Regardless of whether you're utilizing the Cells and Splits feature, Cheetah Digital recommends that you rely on one or more of the following Campaign related entities to achieve this level of uniqueness, as the system-assigned Campaign ID on its own will NOT achieve this goal for you:
-
Campaign Name
-
Campaign Folder structures
-
Campaign Send Date
-
Metadata
Your Messaging solution will differ depending on your specific needs, but this consideration should be addressed when determining your overall requirements for Campaign reporting and/or aggregation purposes, and defining any exports that might be needed in support of those external Messaging Campaign related endeavors.
Back to Getting Started with Messaging