Setting Up Tailored Post-Purchase Offers with Rebuy Tags

·Jul 16, 2025 08:50 PM·

We are setting up our post-purchase offers and would like to tailor the discount based on the customer and/or order details. One example is new customers who use a welcome offer (15% off) on their initial purchase. In this case we wouldn't want to offer a worse discount than what they used on their original order. In the data source setup I see the "Order Tags" option. If we were to use Shopify flow to tag the order upon creation, would Rebuy then be able to act on that tag? My question is really around timing of when Rebuy reads the tag and if the tag has to be on a previous order or the current one. Can anyone on the Rebuy team provide me some guidance here?

9 comments

· Sorted by Oldest

Matt Kanfer
·
·
Hey Brandon - You've got a good idea, just isn't quite possible. Order tag is not viable in Post Purchase since the rules are evaluated during checkout, prior to the order actually happening. There is also not a way within the Data Source to have an "If Discount Code" as an input. I can however think of 2 workarounds. Have a rule within your data source or a separate flow above your other flows with 'If Customer Order Count is Equal to 0 (aka, new customer) return product AND Widget Discount (15% or more) - this assumes that a first time customer would be using the discount code. You'd then show this offer to first time customers but don't have to show it to all customers if you wanted to offer everyone else 10% off. https://help.rebuyengine.com/en/articles/6882645-post-purchase-widgets-features-capabilities-and-limitations-to-consider
Brandon Maskell
·
·
Thanks Matt Kanfer. Are there any plans on the roadmap to support segmenting based on a coupon the customer has applied in cart or on the placed order? When determining offers to present, this is critical as we wouldn't want to show an offer worse than what they already had on the initial order.
Matt Kanfer
·
·
Shopify does not tell us if or what discount code is used on the initial purchase so even if it were an option within Data Sources elsewhere on the site, it would not be in the input payload we could evaluate to match or unmatch rules
Brandon Maskell
·
·
Matt Kanfer when going the new customer route, would I setup the datasource as "Customer Order Count = 0" or "Customer Order Count = 1"? I guess what I'm asking is when is the rule evaluated? After the customer makes the purchase to get to the post-purchase experience or before?
Matt Kanfer
·
·
Good question! The rules are actually evaluated at checkout so new customers will have an order count of 0. Show offer to new customers - Customer Order Count is equal to 0 Show offer to returning customers - Customer Order count is greater than 0 Show offer to someone who just made their fifth purchase - Customer Order Count is equal to 4
🙌1
Brandon Maskell
·
·
One other question. We want to track performance of the same offer between new and returning customers. I assume the recommendation is to then create two duplicate post purchase flows (one for each), as I don't see a way in the reporting to segment by new/returning?
Matt Kanfer
·
·
Correct - 2 flows (both Live), 2 widgets (1 per flow), 2 different matching conditions for the offers to show to either new or returning customers. You'll then get flow based reporting (conversion rate, rpv, etc) and also get widget based reporting.
Brandon Maskell
·
·
Hey Matt. Another question. We're noticing that although have the timer set to 5 min on the post purchase offer, the documentation indicates the order remains on hold for an hour if the customer doesn't explicitly add and item to cart or decline the offers. Is there a way to release that hold as soon as the 5 min to take advantage of the offer expires?
Matt Kanfer
·
·
Correct - though I should be able to grant you beta access to a feature we'll be rolling out soon that allows you to control this. Shoot your MSM Katie Cooper and I DM!

Matt Kanfer
·
·
Hey Brandon - You've got a good idea, just isn't quite possible. Order tag is not viable in Post Purchase since the rules are evaluated during checkout, prior to the order actually happening. There is also not a way within the Data Source to have an "If Discount Code" as an input. I can however think of 2 workarounds. Have a rule within your data source or a separate flow above your other flows with 'If Customer Order Count is Equal to 0 (aka, new customer) return product AND Widget Discount (15% or more) - this assumes that a first time customer would be using the discount code. You'd then show this offer to first time customers but don't have to show it to all customers if you wanted to offer everyone else 10% off. https://help.rebuyengine.com/en/articles/6882645-post-purchase-widgets-features-capabilities-and-limitations-to-consider
Brandon Maskell
·
·
Thanks Matt Kanfer. Are there any plans on the roadmap to support segmenting based on a coupon the customer has applied in cart or on the placed order? When determining offers to present, this is critical as we wouldn't want to show an offer worse than what they already had on the initial order.
Matt Kanfer
·
·
Shopify does not tell us if or what discount code is used on the initial purchase so even if it were an option within Data Sources elsewhere on the site, it would not be in the input payload we could evaluate to match or unmatch rules
Brandon Maskell
·
·
Matt Kanfer when going the new customer route, would I setup the datasource as "Customer Order Count = 0" or "Customer Order Count = 1"? I guess what I'm asking is when is the rule evaluated? After the customer makes the purchase to get to the post-purchase experience or before?
Matt Kanfer
·
·
Good question! The rules are actually evaluated at checkout so new customers will have an order count of 0. Show offer to new customers - Customer Order Count is equal to 0 Show offer to returning customers - Customer Order count is greater than 0 Show offer to someone who just made their fifth purchase - Customer Order Count is equal to 4
🙌1
Brandon Maskell
·
·
One other question. We want to track performance of the same offer between new and returning customers. I assume the recommendation is to then create two duplicate post purchase flows (one for each), as I don't see a way in the reporting to segment by new/returning?
Matt Kanfer
·
·
Correct - 2 flows (both Live), 2 widgets (1 per flow), 2 different matching conditions for the offers to show to either new or returning customers. You'll then get flow based reporting (conversion rate, rpv, etc) and also get widget based reporting.
Brandon Maskell
·
·
Hey Matt. Another question. We're noticing that although have the timer set to 5 min on the post purchase offer, the documentation indicates the order remains on hold for an hour if the customer doesn't explicitly add and item to cart or decline the offers. Is there a way to release that hold as soon as the 5 min to take advantage of the offer expires?
Matt Kanfer
·
·
Correct - though I should be able to grant you beta access to a feature we'll be rolling out soon that allows you to control this. Shoot your MSM Katie Cooper and I DM!