For feature details, please refer to: Feature Overview|Retargeting
Retargeting can be configured using different data source modes. Please ensure your brand has completed the required integrations and prerequisites before following the setup steps below.
Step 1: Prerequisite Checks
-
GA4-only Mode
- MAAC e-commerce feature is enabled, and GA4 integration is complete. For GA4 setup and permissions, refer to: How to share GA4 access and Product feed with Crescendo Lab to enable EC plan?
- GA4 must include cart-related event data:
- Go to GA4 Admin Click on “Lifecycle” > “Monetization” > “E-commerce Purchases” Click “Shopping Behavior”, and verify that the “Adds-to-Carts” event shows numbers, and each product has corresponding data.
- Retargeting campaigns must use MAAC tracking links with UTM parameters, or use MAAC’s audience segment tool with UTM settings applied.
⚠️ Only mobile-originated traffic can be linked back to LINE UID; desktop clicks cannot be tracked. UTM must include utm_term. For example: https://www.cresclab.com/utm_campaign=tracelink_xxxx&utm_source=line&utm_medium=message&utm_term=lm%3A5
- Retargeting campaigns must use MAAC tracking links with UTM parameters, or use MAAC’s audience segment tool with UTM settings applied.
- Go to GA4 Admin Click on “Lifecycle” > “Monetization” > “E-commerce Purchases” Click “Shopping Behavior”, and verify that the “Adds-to-Carts” event shows numbers, and each product has corresponding data.
-
GA4 + SDK Mode
- In addition to GA4 requirements, Web SDK must be installed.
- Setup instructions: SDK installation instructions
-
SDK-only Mode
- Retargeting is based solely on Web SDK user behavior tracking.
- Go to: Admin Center > Tool Settings > Web Footprint Tracking and turn it off. This disables SDK tracking while keeping Web Channel connected.
- Access path: Retargeting >Setting > Website Behavior Tracking > Setting > Channel Settings > Connected Websites > Web Tools > Web Footprint Tracking
Step 2: Configure Retargeting
Go to: MAAC > Automation > Retargeting > Settings, and follow the steps below:
1. Define Trigger Conditions
Set a delay time for when the reminder is sent after the cart event (e.g., 4 hours). Recommendation for GA4 mode: Set a delay of over 24 hours (ideally 36 hours) to avoid delivery issues due to data latency.
You can also set:
Sleep Hours: Avoid sending during night hours.
Step 3: Create Retargeting Message
Go to: MAAC > Automation > Retargeting > Create
- Set message contents
- Use the “Unpaid Items” Dynamic Message Template, which automatically pulls up to 10 product entries (image, name, price).
⚠️ Each retargeting message can include only one dynamic cart module.
- Use the “Unpaid Items” Dynamic Message Template, which automatically pulls up to 10 product entries (image, name, price).
- Set UTM tracking
- Ensure all redirect links include UTM parameters to enable performance tracking.
- Dynamic Message will auto-map to corresponding product URLs from the Product Feed.
- Save & Schedule
- You may save the message as a draft and return to edit it later.
- Set a scheduled send time. The system will deliver the message automatically at the chosen time.
Performance Reports
You can access performance metrics for all Cart Retargeting messages via the MAAC backend dashboard. Use the reporting tools to evaluate each campaign and refine your strategies.
Key performance metrics include:
Delivery count, Open rate, Click rate, Order count, Revenue. Click the report icon to view product-level click details and card previews. Use the export function to download performance data for specific periods.
Data Sources
-
GA4:
- Data comes from UTM-marked traffic reported to Google Analytics 4.
- 24–72 hour data latency. Best for historical analysis.
- May differ from SDK data.
-
SDK:
- Data is reported in real-time (usually < 1 hour).
- Tracks:
- Number of interactions (e.g., clicks, cart adds)
- Number of unique users who triggered interactions
- Best for real-time campaign monitoring and dynamic message tracking.
-
GA4 + SDK
- The system provides tabs to switch between GA4 and SDK metrics within the report dashboard.
- We recommend using both to cross-validate data and optimize campaigns.
Data Comparison Summary
| Data Source | Technology Used | Data Latency | Dynamic Message Support |
|---|---|---|---|
| GA4 | UTM tagging & GA4 backend | 24–72 hours | Yes |
| SDK | Embedded tracking script | Real-time (<1h) | Yes |
Note: GA4 and SDK use different data collection methods. Metrics may vary. Choose the appropriate mode based on your retargeting goals.
FAQ
Q: Why isn't the Abandoned Cart Retargeting triggering after setup?
If you find that the Abandoned Cart Retargeting is not working, it is usually related to the SDK setup status or the tracking mechanism (UTM identification). Please follow the steps below to check:
1. Check Web Channel and SDK Settings
Please go to Admin Center > Channel Settings and confirm:
Is the Web Channel enabled?
-
Is the SDK setup complete?
If the channel is enabled but the SDK is not implemented, the system will not receive behavioral data.
Refer to: [Tutorial | SDK Web Behavior Tracking Tool]
2. Confirm the Tracking Mechanism (Key Reason)
For "Abandoned Cart Retargeting" to function properly, in addition to connecting the SDK and uploading the product catalog, the system must be able to bind the "Website Visitor" to a "LINE Friend."
The specific trigger process is as follows:
Click a Tracking Link: The consumer must use their mobile phone to click a link created by MAAC that contains UTM parameters (e.g., Broadcast messages, Rich Menu links).
Identity Identification: When a friend enters the website via that link, the system can identify "which LINE friend this visitor is."
Trigger Condition: Retargeting reminders will only be triggered if the system successfully identifies the user and they add items to the cart without completing the checkout.
⚠️ Note: If you have not yet sent a link containing UTM parameters, or if consumers do not enter the site through these links, the system cannot identify their LINE identi