Problem
An Email campaign with personalized event attributes encounters an issue where everything works properly except for one specific attribute. This occurs after publishing the campaign, despite no problems during testing or preview.
Solution
To resolve the issue of personalized campaigns not working properly, it is necessary to avoid using event attributes reserved by MoEngage in the campaign's backend.
info |
Information
MoEngage reserves certain event attribute names to ensure the system operates effectively. These event attributes are:
- Campaign Id
- Readable Campaign Id
- Parent Campaign id
- Parent Flow Id
- Parent Flow Name
- Campaign Name
- Campaign Type
- Variation Id
- Locale Id
- Locale Name
- Card ID
- Card Category
- Control Group Type
- Version Name
- Version Id
- Campaign Channel
- Campaign Content Type
- Delivery Type
- Attribution Type
- Goal Type
- Goal Name
- Revenue
- Time to convert
- Campaign Tags
- Facebook Ad Account ID
- Facebook Audience ID
- Facebook Audience Name
- Facebook Audience Sync Type
- Facebook Audience Sync Attributes
- Google Ads Audience ID
- Google Ads Audience Name
- Google Ads Audience Account ID
- Google Ads Audience Login Customer Id
- Google Ads Audience Sync Type
- Google Ads Audience Sync Attributes
- Flow Trip Id
- User Type
- Flow Id
- Flow Name
- Flow Conversion Event
- Flow Action Campaign Id
- Stage Name
- Stage Id
- Transaction ID
- Request ID
- Alert ID
- Alert Channel
- Alert Name
- Request Type
- Notification Type
- Formatted Alert ID
- Inform Tags
- Delivery Description
- Message Parts
- Time to deliver
- Time to Send
- MOE Event Category
- MOE Event Source
- email subject
|