Feature Snapshot
Summary:
Acceptance criteria are a set of upfront validation rules applied to every lead to confirm that required fields (such as email, phone, and date) contain correctly formatted data, while filtering applies later in the flow using enhanced or additional data to block leads that would otherwise be rejected.
Key Benefits:
- Saves processing costs by blocking unqualified leads before expensive enhancements are invoked
- Enhances data quality by ensuring that only leads with critically valid information enter the flow
- Allows for tailored validation by applying universal (flow-level) or vendor-specific (source-level) rules; pings are checked against the same rules, skipping any rule whose field was not sent
- Provides clear, actionable feedback to sources for troubleshooting data submission errors
Typical Use Cases:
- Campaigns that mandate the presence and correct formatting of key data elements (e.g., valid email, phone number, and date fields)
- Flows where different vendors require customized data checks through source-level acceptance criteria
- Real-time bidding scenarios, where a ping is checked against the flow’s and source’s acceptance criteria using only the fields sent in the ping
- Systems that combine upfront rejection with mid-flow filtering based on enhancement outcomes
How the Acceptance Criteria and Filtering Distinction Works?
Acceptance criteria operate at the very beginning of a lead flow. They are applied on two levels:
- Flow-Level Acceptance Criteria: Universal rules that every lead must pass, such as checking that required fields are not blank and properly formatted.
- Source-Level Acceptance Criteria: Customized rules specific to individual lead vendors or partners, tailoring validations (like mandatory campaign IDs) to their unique data submission patterns.
A ping is checked against the same flow-level and source-level criteria; a rule whose field was not sent in the ping is skipped.
When a lead fails, the source receives the configured outcome and a reason: the reason set on the criteria or, if none is set, a generated one naming the field and requirement (for example lead.first_name must be equal to bob).
In contrast, filters are usually invoked later in the flow after some data enhancements have taken place and are used to block leads based on additional, often dynamic, criteria that cannot be determined at the time of submission.
Step‑by‑Step Instructions
- Define Required Fields:
Identify the critical data (such as email, phone, and dates) that every lead must have and note the acceptable formats.
- Configure Flow-Level Acceptance Criteria:
In your flow’s settings, add rules (using operators like “is not blank” and “format is valid”) that universally validate every incoming lead.
Expected Result: Leads missing essential data or featuring invalid formatting are immediately rejected. The rejected lead is still recorded as a source event carrying the outcome and reason returned to the source; no flow step runs for it.
- Configure Source-Level Acceptance Criteria:
For sources with distinct requirements (for instance, a vendor that must provide a specific campaign identifier), add source-level rules to enforce these vendor-specific conditions.
Expected Result: Only leads from that vendor passing the custom criteria continue into the flow.
- Real-Time Bidding (Pings):
No separate setup is needed: a ping is checked against your flow-level and source-level criteria, and any rule for a field not included in the ping is skipped.
Expected Result: A ping that passes the criteria receives asuccessresponse with the price the flow would pay; one that fails receivesfailurewith the reason. - Test the Setup:
Submit a variety of test leads—including leads with missing, misformatted, or borderline values—and verify in your LeadConduit dashboard that rejection reasons and accepted leads are correctly processed.
Validation & Monitoring (optional)
- Test the Setup:
Run test submissions and observe the lead event logs to ensure that leads failing acceptance criteria are blocked immediately. - Where to Monitor?:
Check the rejection logs and event details on your LeadConduit dashboard, particularly focusing on source and filter events to track which criteria are triggered.
Best Practices
- Prioritize Fundamental Checks:
Always enforce basic validations (e.g., “is not blank” for email, phone, and date) at the very start of the flow to avoid wasting resources on invalid leads. - Tailor Rules for Each Source:
Use source-level criteria to customize requirements for different vendors, reducing false rejections and ensuring consistency across flows. - Combine Acceptance and Filtering Strategically:
Use acceptance criteria for initial, critical validations and complement these with mid-flow filters that leverage enhanced data to catch additional issues. - Test and Monitor Regularly:
Continuously test your configurations with varied lead data, and adjust rule thresholds based on rejection patterns and conversion rates. - Keep Rules Simple and Clear:
Use straightforward operators (e.g., “is not blank”) to avoid overly complex logic that can lead to unpredictable outcomes and troubleshooting challenges.
Troubleshooting
| Symptom / Error | Likely Cause | Resolution |
|---|---|---|
| Leads missing required information are not being rejected | Criteria rules may be misconfigured (wrong operator or threshold) | Review rules to ensure they explicitly check for non-blank fields and valid formats. |
| Valid leads are being blocked | Rules may be too strict or not account for acceptable data variation | Adjust rule thresholds and operators; validate with sample leads to fine-tune the criteria. |
| Inconsistent lead rejection across sources | Source-level criteria misalignment or differing field naming | Standardize mappings and criteria across sources; verify field alignments in mapping settings. |
Frequently Asked Questions (FAQ)
Why use acceptance criteria instead of filtering for required fields?
Acceptance criteria run as the lead first enters the flow, blocking leads missing crucial data—this early rejection saves processing costs and prevents unnecessary enhancements.
When should I use filtering rather than acceptance criteria?
Filtering is appropriate when decisions depend on data that becomes available only after enhancements (e.g., phone validation outcomes) or when conditional logic based on dynamic information is needed.
What is the difference between flow-level and source-level acceptance criteria?
Flow-level criteria enforce universal rules for every lead in a flow, while source-level criteria allow for customized rules tailored to specific lead vendors.
How are pings checked against acceptance criteria?
There are no separate ping-level criteria: a ping is checked against the flow’s and source’s acceptance criteria, and a rule whose field was not sent in the ping is skipped.
Can acceptance criteria and filtering be used together?
Yes, combining both is recommended—acceptance criteria perform the initial, broad check and filtering adds an extra layer of quality control based on enhanced or delayed data.
Glossary
| Term | Definition |
|---|---|
| Acceptance Criteria | A set of pre-processing rules that validate the basic required fields and formatting of a lead before any further processing or enhancements occur. |
| Flow-Level Criteria | Acceptance rules applied to every lead in a flow, ensuring that universal data quality standards are met for all incoming leads. |
| Source-Level Criteria | Specific rules applied to leads from a particular source or vendor, enforcing tailored data requirements unique to that source’s submission. |
| Pings | A ping is checked against the flow-level and source-level criteria; a rule whose field was not sent in the ping is skipped. |
| Filtering | The mid-flow process that uses additional, often enhanced, data to block leads from progressing further in the flow when they are deemed unqualified. |
- ac-fields.png100 KB
- ac-flow.png300 KB
- ac-source.png300 KB
Comments
0 comments
Please sign in to leave a comment.