Product retargeting emails remain gated behind legacy automation
Merchants are asking why the product retargeting email option stays out of reach, and the answer sits in account history and store support.
A question keeps returning to the French-language help pages: where does the product retargeting email actually live, and why does the option refuse to show up? An accepted answer from Intuit settles it. The feature is not a general setting that any account can switch on. It is classed as a legacy automation, and access depends on two things that have nothing to do with the menus a merchant is searching.
The option sits behind an account history check
Product retargeting only appears on paid accounts where a legacy automation has already been created at some point. That single condition explains most of the confusion. A store can be fully paid up, active and busy, and still see nothing at all. Nothing is broken in that case. The door is simply not built into the account, and no amount of clicking around the automation library will add it.
Store support decides whether the checklist appears
The second gate is the store connection. Retargeting works for storefronts linked through a supported e-commerce integration, or through a custom connection the platform accepts. Eligibility is easy enough to test. Open the integrations area, select the connection by name and read the feature list attached to it. If retargeting is missing from that list, the automation cannot be built for that store.
One retargeting email per connected store
Each connected store carries a single retargeting email. A merchant running several storefronts therefore manages several of them, but one storefront cannot hold two competing versions. Treat the message as the permanent one for that store and edit it when the wording needs to change. Setting up a second copy is not an option the platform offers.
Tracking begins with the campaign link
The mechanism is browser-based. A cookie records activity once a subscriber arrives at the store, and it keeps recording for a year, or until that person clears cookies. The entry point is the part merchants miss. A subscriber has to reach the store through a link inside a campaign before any tracking starts. Direct visits, bookmarks and typed addresses do not begin the process. A merchant who sends no linked campaigns sees an empty queue and assumes the automation has failed.
Frequency caps and purchase suppression keep the queue short
Three rules trim the list further. A subscriber receives at most one retargeting email in any seven day window. No retargeting email goes out if the person bought the target product in the meantime. And none goes out if an abandoned cart email for that same product is already on its way. These conditions exist to stop repetitive content reaching the inbox. A low send count is normal, and it is not a symptom of a broken setup.
Building it from the automations area
Open the automations area and step into the discovery view for legacy automations. Choose the e-commerce tab, then pick the option that assigns a new target to site users. Select the store from the dropdown and confirm to begin. The platform then presents a checklist covering delays, product selection and the remaining settings. Our reading of the accepted answer is that this checklist deserves attention before publishing, because the delays decide how long a subscriber waits before the email arrives.
Where the gates leave a merchant
If the store connection is unsupported, or the account has no legacy automation behind it, the feature stays closed. Nothing in the settings will change that, and rebuilding the connection rarely helps. The realistic alternatives are a standard campaign carrying product links, or an abandoned cart flow where one is available. Retargeting is a convenience for stores that already qualify, not a switch every account can flip.