Send email only to to new registrations | Community
Skip to main content
New Member
December 24, 2024
Solved

Send email only to to new registrations

  • December 24, 2024
  • 1 reply
  • 878 views

Hello ACS Experts,

 

I have a workflow that runs every 10 minutes. User fills some information on a landing page created outside ACS. Fills out fields like email address, name, language, country, postal code, product type, product name, product code and date of purchase. This information flows to ACS via API and I map them to the email that is going to be sent via the workflow. I mapped the information through freetext fields.

 

The issue is I want this workflow send 1 email for every product registration. A user can register multiple products and should get only one email per registration. Currently whenever the workflow runs every user who registered a product constantly gets the same email every 10 minutes. I need a way to cut the emails sent to 1. So that when a user registers a product he only gets 1 email not the same email every 10 minutes. If the same user registers another product he gets another(1) email for that product.

 

Thanks

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by harishpandey

Hi @mert_alier,

To ensure users receive only one email per product registration, you can leverage Incremental Queries within your workflow. Here's how you can implement this:

Solution: Use Incremental Query to Filter New Registrations

  1. Configure the Incremental Query Activity:

    • Add an Incremental Query activity to your workflow.
    • Set it to filter records based on the registration timestamp or other relevant criteria, such as "records received in the last 10 minutes."
    • This ensures only new product registrations are processed during each workflow execution.
  2. Deduplicate Records:

    • If the same user registers multiple products within the query timeframe, use a Deduplication Activity or filtering logic to ensure that each product registration is treated as a unique record.
  3. Flag Processed Records:

    • Once an email is sent for a registration, update a field (e.g., a "Processed" flag or timestamp).
    • This helps avoid reprocessing the same record during subsequent workflow runs.

Key Considerations

  • Use Tracking Logs or a dedicated field in your schema to track email sends and avoid duplicate sends.
  • If the external system can provide a unique identifier for each product registration, use this to map and manage deduplication more efficiently.

For more detailed steps and examples, you can refer to the documentation on Incremental Queries:
https://experienceleague.adobe.com/en/docs/campaign-standard/using/managing-processes-and-data/targeting-activities/incremental-query

 

Regards,
Harish Pandey

1 reply

harishpandeyAdobe EmployeeAccepted solution
Adobe Employee
January 3, 2025

Hi @mert_alier,

To ensure users receive only one email per product registration, you can leverage Incremental Queries within your workflow. Here's how you can implement this:

Solution: Use Incremental Query to Filter New Registrations

  1. Configure the Incremental Query Activity:

    • Add an Incremental Query activity to your workflow.
    • Set it to filter records based on the registration timestamp or other relevant criteria, such as "records received in the last 10 minutes."
    • This ensures only new product registrations are processed during each workflow execution.
  2. Deduplicate Records:

    • If the same user registers multiple products within the query timeframe, use a Deduplication Activity or filtering logic to ensure that each product registration is treated as a unique record.
  3. Flag Processed Records:

    • Once an email is sent for a registration, update a field (e.g., a "Processed" flag or timestamp).
    • This helps avoid reprocessing the same record during subsequent workflow runs.

Key Considerations

  • Use Tracking Logs or a dedicated field in your schema to track email sends and avoid duplicate sends.
  • If the external system can provide a unique identifier for each product registration, use this to map and manage deduplication more efficiently.

For more detailed steps and examples, you can refer to the documentation on Incremental Queries:
https://experienceleague.adobe.com/en/docs/campaign-standard/using/managing-processes-and-data/targeting-activities/incremental-query

 

Regards,
Harish Pandey