A/B test campaign related

[rishabhc4656042]

Hi ,

I have been using the A/B feature for my previous client perfectly , however with the new requirements I wish to seek guidance on the below queries.

1) Instead of using 2 separate deliveries to set up a campaign and use the tracking information for targeting the winner, can this be done using a single delivery by implementing dynamic subject lines.
2) It usually takes a lot of time in our instance to get the tracking information . Is there a way that we can expedite the tracking process or what is the exact time when the tracking information is available to use.

3) Are there any challenges that may arise for using recurring deliveries for creating an A/B test campaign.

Thanks.

[Vipul_Raghav]

Hi rishabhc46560428,

Can you please confirm if the request is for Campaign Classic or Campaign Standard?

If it is Classic, you will have to go with the older implementation of having 2 test deliveries each with same content but a different subject.

If you are using Standard, you just need to create a single delivery and use the AB test by subject template to define test criteria. System will take care of login internally.

For tracking, is your tracking and marketing instance hosted by Adobe or some of it is on-prem?

Regards,
Vipul

[rishabhc4656042]

Hi Vipul,
Thank you for the valuable inputs.
Regarding the tracking , our instance is hosted by Adobe.

[Vipul_Raghav · Accepted solution]

Thanks for clarifying rishabhc46560428​

Slowness can be attributed to one of more of the following

1. Tracking workflow by default runs every hour. Probably you are checking for tracking data every minute. We advise against reducing it to less than 1 hour
2. Probably you are sending emails to a lot of customers, millions per hour and hence there is a lot of tracking data being generated which then takes some time to be consumed by trackinglogd process and tracking workflow.
3. Your trackingLogRcp table is bloated currently and hence needs vacuuming to see faster inserts and updates. Worth checking with support to provide you with DB Usage Report which will indicate the level of bloat and you can request for vacuum accordingly.