SOLVED

Trigger Campaigns track in AB testing Email program

Go to solution
Suneka
Level 2

Trigger Campaigns track in AB testing Email program

Hey Community,

Just wanted to know whether we can track the metrics ( Email opens, Clicks, Delivered) using trigger campaigns in the AB testing Email program set up. Initially I used the email program and added AB testing to it and scheduled it fixing the sample as 50%-50%. Before scheduling it I also activated the required trigger campaign to track the opens, clicks and delivered metrics. Unfortunately, the trigger campaigns didn't track the metrics as expected. Can anyone please let me know whether it is feasible to track using triggers?.

 

 

1 ACCEPTED SOLUTION

Accepted Solutions
Darshil_Shah1
Level 10 - Community Advisor

Re: Trigger Campaigns track in AB testing Email program

We were able to figure this out! There was an issue with the email name in the trigger.

 

When an A/B test is added to an email in the email send program, Marketo renames it as <Program Name.Name of Test>. I've always known that the test name gets added to the email name as <Program Name.Email Name.Email Test Name>, i.e, the email name is preserved and not replaced by the test name itself, but it's otherwise now.

View solution in original post

15 REPLIES 15
Darshil_Shah1
Level 10 - Community Advisor

Re: Trigger Campaigns track in AB testing Email program

Do you see the corresponding email activities in the lead activity log? You can create an SL to check to filter out people who engaged with the email. Use filters like Clicked Link in Email, Opened Email, etc., similar to the ones that you have added in the trigger campaign. We'd need to see the campaign setup to see why the campaign didn't fire even though there were engagements logged for the people post campaign was activated.

 

Suneka
Level 2

Re: Trigger Campaigns track in AB testing Email program

Hey Darshil, thanks for the response.

I checked in the Activity log and it is tracking good. I knew that it can be found using SL after deployment but the case is we need to track using the trigger campaigns as we do in normal email program to sync the statuses automatically to the CRM. Only the trigger campaigns were not tracking. Please refer to the set up which I have followed. 

 

Suneka_0-1675886515946.png

 

Darshil_Shah1
Level 10 - Community Advisor

Re: Trigger Campaigns track in AB testing Email program

I see the email send program has already been deployed. Given that the campaigns were activated before the engagements were logged, could you please share snapshots of the smart list, campaign flow, and schedule tabs of one of your campaigns? Also, on a side note, triggers listen for the corresponding lead activity in the act. log, they aren't limited to any asset/program type. Given that you've got a trigger campaign correctly setup, you should see people flowing through the campaign.

 

Suneka
Level 2

Re: Trigger Campaigns track in AB testing Email program

Here you go with the smartlist and flow which I have configured in one of the trigger campaigns.
1. Smart list

Suneka_0-1675957607066.png

2. Flow

Suneka_1-1675957713377.png
For Subject line testing in the set up, I have configured in the way as below:

Suneka_2-1675957939353.png



Whenever I set the test sample size the trigger campaigns were not working. If I remove the test sampling and send it as a one singe email as like a normal email program then the trigger campaign are working good. Please let me know for any feasibility to track using trigger campaigns.

 

Darshil_Shah1
Level 10 - Community Advisor

Re: Trigger Campaigns track in AB testing Email program

Thank you for sharing the snapshots, @Suneka.

 

Two things to check here -

 

-> Do you see deliveries in the email dashboard?

-> Could you confirm whether the campaigns were activated before the emails were sent out? As you'd know, triggers are forward looking. They don't let anyone based on past activity in campaign flow. Also, triggers work well with the AB test given that they're setup correctly.

 

I see you have a "." as the last visible character in the email name constraint in the trigger, and no squiggly line meaning that you most likely have the correct email selected with "Subject Line Test" suffix added in the email name.

 

Suneka
Level 2

Re: Trigger Campaigns track in AB testing Email program

Hi again,

 

Sharing you the updates reg the Email naming convention. Meanwhile it is not a "." , My email and the program name are same.
Please find the screenshot of my email name attached (which pulls up the actual behavior ( Program name, Email program name followed by Email name).

Suneka_0-1675965054176.png

also this,

Suneka_1-1675965134077.png

 

 

Darshil_Shah1
Level 10 - Community Advisor

Re: Trigger Campaigns track in AB testing Email program

Gotcha - "." is the separator used by the system to refer to the nested assets in a program (e.g., <Program Name.Email Asset Name>)!

 

FYR - the email name with AB test has the test type added as suffix in the name (e.g., I've a Subject Line test added to the email, and the same needs to be included in the email name constraint). I think, @Katja_Keesom was also talking on the similar lines in her comment earlier. If you don't add the test type suffix in the email name, you'd need to use "starts with" operator instead of "is" operator.

Darshil_Shah1_0-1675965436264.png

 

Suneka
Level 2

Re: Trigger Campaigns track in AB testing Email program

Thanks, I just tried using the operator as " starts with" instead of "is". But still there is no expected tracking. I just sent an internal test for 50% of the list and tried. Is there something wrong with anything else?. 

Suneka_0-1675969826384.png

 

Darshil_Shah1
Level 10 - Community Advisor

Re: Trigger Campaigns track in AB testing Email program

I see. I think it’d be better if we could connect over a call to debug this. If you DM me here in the community, we can find some time to connect tomorrow in the daytime IST, or later in the evening IST if you’re located in a  western timezone. For everyone’s visibility, I can post an update here once we figure out what the real issue was.