My “message contains” automations are triggering (not sure if running correctly) , but unlike post or Reels reply automations, which have a high CTR, all of my “message contains” automations show CTR as N/A. Why does this happen? Is there something wrong with them?
Here how it shows:
Here the start of my automation (i guess all the 72% of CTR came from “User comments on your Post or Reel”):
Is this right?
Or when user sends a message the first step automatically bypassed?
Best answer by cata_rendon
Hi
Since CTR is calculated at the message level, any user who reaches that message (regardless of which trigger they came from) can be part of that percentage.
If you want to attribute the CTR by trigger, the approach you can take is the following:
Create a small pre-flow per trigger
Tag the user or set a custom field indicating the entry source (e.g. Comment vs DM keyword)
Then send everyone into the shared flow with the messages you’re analyzing
That way, even though the message shows a single aggregated CTR, you can later filter users and clearly see which trigger contributed to those clicks.
My advice: create a new flow for this analysis and stop using the current one, since existing traffic will bias the metrics.
So yes — the metric is shared, but the source can be identified with proper pre-flow tagging.
Hope this helps clarify it 🙂
Cheers
Cata Rendon
+4Hi
Since CTR is calculated at the message level, any user who reaches that message (regardless of which trigger they came from) can be part of that percentage.
If you want to attribute the CTR by trigger, the approach you can take is the following:
Create a small pre-flow per trigger
Tag the user or set a custom field indicating the entry source (e.g. Comment vs DM keyword)
Then send everyone into the shared flow with the messages you’re analyzing
That way, even though the message shows a single aggregated CTR, you can later filter users and clearly see which trigger contributed to those clicks.
My advice: create a new flow for this analysis and stop using the current one, since existing traffic will bias the metrics.
So yes — the metric is shared, but the source can be identified with proper pre-flow tagging.
Hope this helps clarify it 🙂
Cheers
Cata Rendon
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
