Overview
The Lead Within Time Period Processr job is designed to flag leads that have fallen outside of a specific time period set by the user.
While it is based on the createdTs field by default, it can be mapped to look at a custom field on the lead, allowing you to invalidate leads based on any other date fields that you may have captured, such as opt-in dates or asset download dates, publisher capture dates etc.
Note: The date has to be in YYYY-MM-DD format for this processr job to work.
Configuration
1. Within your campaign, navigate to the Processr tab.
2. Click Add Job and select Lead Within Time Period from the dropdown list, then click Save.
3. While adding the Proccesr job you can configure the settings. By default, the job is configured to the createdTs field, which is the system timestamp appended to the lead at the time of capture.Note: With the configuration, we recommend using configuration presets (see bottom of the page), or you can enter this manually.
4. In the below example, the configuration is set up for a typical scenario where your client has specified that the lead cannot be valid if the specified date on the lead is older than a week. Now you can see the default settings, where the Start_datetime and End_datetime can be configured.
5. You may have a scenario where the date needs to be based on a field value. The settings can be configured to reference this lead field. In the below example, the Processr job has been configured to invalidate leads which have a response_date value which is greater than 1 week earlier than the current system date at the time of capture.
For example, if today's date is February 19th and a lead had the response_date of 2025-02-11 that lead would be invalidated.
6. To configure the above, click 'Add' under the Mapping section.
7. Add createdTs in the left field, and type your custom field name in the right field.
8. Click Save.
Presets
Use these for 'Start Date Time' and 'End Date Time'
| Configuration | Description |
|---|---|
| today | This uses the current system timestamp of when the lead was captured |
| +1 day | This uses the current system timestamp of when the lead was captured + 1 day (the 1 can be edited to any number you choose for instance changing to + 7 day will extend the range to 7 days) |
| -1 day | This uses the current system timestamp of when the lead was captured - 1 day (the 1 can be edited to any number you choose for instance changing to - 7 day will extend the range to 7 days) |
| +1 week | This uses the current system timestamp of when the lead was captured + 1 week the 1 can be edited to any number you choose for instance changing to + 4 week will extend the range to 4 weeks) |
| -1 week | This uses the current system timestamp of when the lead was captured - 1 week (the 1 can be edited to any number you choose for instance changing to - 4 week will extend the range to 4 weeks) |