You send a review request seven days after purchase. Maybe fourteen. The automation fires, the email goes out, and then… nothing. The contact sits in your list with no indication whether they left a five-star love letter or a one-star rant about your shipping time.
That's not a review workflow. That's a dead end with a form at the bottom.
The pattern I see in most accounts: review requests are treated as broadcast messages instead of conversation starters. ActiveCampaign sends the ask. The reviews platform captures the response. And the two systems never speak again. You're flying blind on your happiest customers and your most frustrated ones, and both groups are getting the same generic monthly newsletter.
The Loop That Actually Works
Here's the structure that turns review requests into actionable contact data:
- ActiveCampaign triggers the review request automation based on purchase behavior
- The reviews platform captures the response and rating
- The platform sends the rating data back to ActiveCampaign via webhook or native integration
- ActiveCampaign tags the contact based on rating tier
- Tags trigger conditional automations: positive reviewers flow into VIP/UGC-request sequences, negative reviewers flow into customer-save workflows
Every step feeds the next one. The review isn't the end—it's the entry point into a smarter retention system.
Most ActiveCampaign users stop at step two. They send the request, collect reviews on the platform, and maybe glance at the dashboard once a quarter. The contact record in ActiveCampaign shows a purchase tag and nothing else. You're sitting on segmentation gold and leaving it in someone else's database.
Field Mapping: Getting Review Data Into ActiveCampaign
The mechanics depend on which reviews platform you're using. Judge.me, Stamped, Yotpo, Loox, Okendo—most of them can push data back into ActiveCampaign via webhook or Zapier. Some have native integrations. Either way, you need three data points to make this work:
- Review rating (1–5 stars)
- Review submitted date
- Review text (optional but useful for UGC workflows)
If your platform supports webhooks, configure it to fire when a review is submitted. Point the webhook at ActiveCampaign's event tracking endpoint. Map the rating value to a custom field—I use a field called Last Review Rating—and map the timestamp to Last Review Date.
If you're using Zapier or Make, the flow is the same: trigger on new review, send the rating and timestamp to ActiveCampaign as a custom field update. Include the contact's email address in the payload so the integration can match the right record.
The review text itself is harder to pass cleanly because it's long-form. If you want it in ActiveCampaign for future reference, create a custom field called Last Review Text with a text area type. Most programs don't need this field to run the automations, but it's useful if you're manually sorting for UGC requests later.
Tag-Based Routing: What Happens After the Review Comes In
Once the rating hits ActiveCampaign, you need an automation to evaluate it and apply the right tag. This is where most setups break down—people store the rating in a custom field and then do nothing with it.
Build a simple automation triggered by Last Review Rating field update. Use conditional splits to route based on rating value:
- If
Last Review Ratingis 5, add tagReview: Promoter - If
Last Review Ratingis 4, add tagReview: Passive - If
Last Review Ratingis 1, 2, or 3, add tagReview: Detractor
You can get more granular if you want, but three tiers is enough for most programs. The tag is what actually triggers the downstream automations. The custom field stores the data; the tag drives the action.
I configure this as a standalone automation rather than bolting it onto the review request sequence. That way it runs regardless of how the review was submitted—whether it came from your post-purchase email, a review reminder, or a direct link someone clicked two months later.
The Promoter Path: VIP Treatment and UGC Requests
Contacts tagged Review: Promoter are your highest-signal segment. They bought, they loved it, and they told you so in public. Don't waste that momentum.
Build an automation that starts when the Review: Promoter tag is added. Wait one day—let them enjoy the afterglow of leaving a nice review—then send a thank-you email with a specific ask. The two paths that work:
Path one: referral or affiliate invitation. If you run a referral program, this is the warmest possible entry point. "Thanks for the review—want to share with friends and earn X?" The conversion rate on this email is higher than any cold referral pitch because the contact just publicly endorsed you.
Path two: UGC request. Ask for a photo, video, or case study. Frame it as an extension of the review they already left. "We loved your review—would you be open to sharing a quick photo of [product] in action?" If you're running paid social, this is how you build a UGC library without paying influencers.
Tag contacts who say yes with UGC: Submitted or Referral: Active so you can segment them later. Add them to a VIP list if you have one. These people are your amplifiers—treat them differently than the rest of your list.
The Detractor Path: Customer-Save Before They Churn
Contacts tagged Review: Detractor are flight risks. They're frustrated enough to leave a low rating, which means they're already halfway out the door. If you do nothing, they churn quietly. If you respond fast, you can save a meaningful percentage of them.
Build an automation that starts when the Review: Detractor tag is added. Send an email within 24 hours—not from a no-reply address, from a real human on your team. The subject line: "We saw your review and want to make it right."
The email itself should be short. Acknowledge the issue, apologize without deflecting, and offer a specific remedy: a refund, a replacement, a discount on the next order, or a direct line to support. Include a reply-to address that actually works, and make sure someone is monitoring it.
Use a deal pipeline in ActiveCampaign to track these contacts as they move through the save process. Create a pipeline called Customer Recovery with stages: Contacted, Responded, Issue Resolved, Churned. Move the deal forward as the contact replies and engages. This gives you visibility into how many detractors you're successfully recovering versus how many are walking anyway.
The contacts who respond and resolve the issue should get a second tag: Recovery: Saved. Build a win-back sequence specifically for this group. They've seen you at your worst and decided to give you another shot—that's a relationship worth nurturing.
The Passive Path: The Middle Tier Most People Ignore
Four-star reviewers—tagged Review: Passive—are the forgotten middle. They're not raving fans, but they're not angry either. They're satisfied, which means they're persuadable.
Most programs dump these contacts into the general nurture flow and call it a day. That's a wasted opportunity. Build a light-touch automation that asks a single follow-up question: "What would have made this a five-star experience?"
You're fishing for objections and feature requests. Maybe the product is great but shipping took too long. Maybe the onboarding was confusing. Maybe they wanted a feature you don't offer yet. The responses tell you what's blocking these contacts from becoming promoters.
Store the answers in a custom field or as notes on the contact record. If the same issue comes up repeatedly, you've identified a systemic friction point. Fix it and you move a chunk of passives into the promoter column.
Review Reminders: Don't Ask Once and Disappear
The initial review request automation should not be a single email. If someone doesn't leave a review after the first ask, send a second one seven days later. If they still don't respond, send a third one fourteen days after that.
Use conditional logic to stop the sequence if the Last Review Rating field gets updated—meaning they left a review through a different channel or from the first email and you just haven't seen the webhook fire yet. The goal here is persistence without annoyance.
Each reminder should reframe the ask slightly. Email one: "How did we do?" Email two: "Still curious what you thought—mind sharing?" Email three: "Last nudge—your feedback helps us improve." Don't copy-paste the same message three times.
I configure this as a separate automation triggered by the same purchase event that starts the initial review request. Wait 14 days, check if Last Review Rating is empty, send reminder one. Wait another 7 days, check again, send reminder two. One more 14-day wait, final check, send reminder three. If the field is populated at any point, the contact hits a goal step and exits.
Closing the Loop
The difference between a review request and a review workflow is what happens after the response comes back. Most programs send the ask and hope for the best. The ones that work treat the review as the beginning of a conditional path—promoters get invited into referral programs, detractors get recovery outreach, and passives get nudged toward five stars.
ActiveCampaign can't execute any of that if the review data stays locked in your reviews platform. Close the loop. Map the fields. Tag the contacts. Let the automation decide what happens next.
If you're running ActiveCampaign and you're not sure whether your review workflow is leaking revenue, I'll audit it for free: getner.ai/audit.