Skip to content

Commit 99fc8f0

Browse files
authored
Update 2015-06-16-engage-analyze.md
1 parent 71846de commit 99fc8f0

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

_posts/2015-06-16-engage-analyze.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ summary: You can find more details about how Engage and Analyze work together he
88
{:toc}
99
* * *
1010

11-
# Events in Analyze
11+
# Events in Analyzee
1212

1313
When you create a campaign in Engage you will pass events to Analyze. The events that are passed to Analyze follow the naming convention of “campaign name -” + the following, for example “Test Campaign - eligible”.
1414

@@ -24,4 +24,4 @@ When you create a campaign in Engage you will pass events to Analyze. The events
2424

2525
# Properties in Analyze
2626

27-
In addition to the events that are passed to Analyze, if you chose to A/B test your campaign you will also see the property “campaign name - group”. If the the visitor is shown an Engagement they will receive the value “variation”. If they are not shown an Engagement but match the audience, placement and frequency requirements they will receive the value “control”.
27+
In addition to the events that are passed to Analyze, if you chose to A/B test your campaign you will also see the property “campaign name - group”. If the the visitor is shown an Engagement they will receive the value “variation”. If they are not shown an Engagement but match the audience, placement and frequency requirements they will receive the value “control”.

0 commit comments

Comments
 (0)