Search the Omeda Knowledge Base
-
The Omeda Experience
-
Documentation
-
-
- Brand Comprehensive Lookup Service
- Brand Promotions Quantity
- Brand Group Lookup
- Brand Promotions Content By Promo Code
- Brand Promotions By Promo Code
- Behavior Categories Lookup
- Behavior Actions Lookup
- Behavior Lookup Grouped By Product
- Behavior Lookup By Id
- Behavior Lookup
- Demographic Lookup by Brand API
- Deployment Type Lookup by Brand API
- Product Lookup by Brand API
-
- Customer Lookup By Email Address
- Subscription Lookup By Customer Id
- Order History Lookup by Customer Id
- Customer Lookup by Hashed Email Address
- Email Address Lookup By Customer Id
- Gift Lookup by Donor ID
- Behavior Lookup By Customer Id
- Subscription Lookup By Email
- Customer Merge History Lookup
- Customer Lookup By Name and Country
- External ID Lookup By Customer Id
- Demographic Lookup By Customer Id
- Phone Lookup By Customer Id
- Postal Address Lookup By Customer Id
- Customer Change Lookup
- Customer Comprehensive Lookup By Customer Id
- Customer Lookup By EncryptedCustomerId
- Customer Lookup By External ID
- Customer Lookup By PostalAddressId
- Customer Lookup By Customer Id
- Email Validity Lookup API
- Behavior Attribute Lookup by Customer Id
- Order Issue History Lookup by Customer Id
- Show all articles8 Collapse Articles
-
- Email On Demand Send
- Email Deployment
- Email Deployment Clone
- Email Deployment Remove Audience
- Email Audience Assignment Status
- Email Deployment Content
- Email Deployment Approval Lookup
- Email Deployment Schedule
- Email Deployment Cancel
- Email Deployment Search
- Email Flag Email As Invalid
- Email Clicks
- Email - Checklist for Sends Created via API Calls
- Email Deployment Content Lookup
- Email Deployment Unschedule
- Email Deployment Lookup
- Email Deployment Test
- Email Deployment Add Audience
- Email Opt In/Out Lookup
- Email Optout Queue
- Email Optin Queue
- Email Deployment Audience List FTP
- Show all articles7 Collapse Articles
-
-
- Release Notes for Feb. 2 | V24.2
- Release Notes for Feb. 23 | V24.3
- Release Notes for Mar. 15 | V24.4
- Release Notes for Apr. 5 | V24.5
- Release Notes for Apr. 26 | V24.6
- Release Notes for May 24 | V24.7
- Release Notes for June 7 | V24.8
- Release Notes for June 28 | V24.9
- Release Notes for July 19 | V24.10
-
- Release Notes for Jan 27 | V23.2
- Release Notes for Feb 17 | V23.3
- Release Notes for Mar 10 | V23.4
- Release Notes for Mar 31 | V23.5
- Release Notes for Apr 21 | V23.6
- Release Notes for May 19 | V23.7
- Release Notes for June 2 | V23.8
- Release Notes for June 23 | V23.9
- Release Notes for July 14 | V23.10
- Release Notes for Aug 4 | V23.11
- Release Notes for Aug 25 | V23.12
- Release Notes for Sep 15 | V23.13
- Release Notes for Oct 6 | V23.14
- Release Notes for Oct 27 | V23.15
- Release Notes for Nov 16 | V23.16
- Release Notes for V23.17
- Show all articles1 Collapse Articles
-
- Release Notes for Jan 14 | V22.1
- Release Notes for Feb 4 | V22.2
- Release Notes for Feb 25 | V22.3
- Release Notes for Mar 18 | V22.4
- Release Notes for Apr 8 | V22.5
- Release Notes for Apr 29 | V22.6
- Release Notes for May 20 | V22.7
- Release Notes for June 10 | V22.8
- Release Notes for July 1 | V22.9
- Release Notes for July 22 | V22.10
- Release notes for Aug 12 | V22.11
- Release Notes for Sep 2 | V22.12
- Release Notes for Sep 23 | V22.13
- Release Notes for Oct 14 | V22.14
- Release Notes for Nov 4 | V22.15
- Release Notes for Dec 2 | V22.16
- Show all articles1 Collapse Articles
-
- Release Notes for V21.1
- Release Notes for V21.2
- Release Notes for V21.3
- Release Notes for V21.4
- Release Notes for V21.5
- Release Notes for V21.6
- Release Notes for V21.7
- Release Notes for V21.8
- Release Notes for V21.9
- Release Notes for V21.10
- Release Notes for V21.11
- Release Notes for V21.12
- Release Notes for V21.13
- Release Notes for V21.14
- Release Notes for V21.15
- Release Notes for V21.16
- Release Notes for V21.17
- Show all articles2 Collapse Articles
-
- Release Notes for V20.1
- Release Notes for V20.2
- Release Notes for V20.3
- Release Notes for V20.4
- Release Notes for V20.5
- Release Notes for V20.6
- Release Notes for V20.7
- Release Notes for V20.8
- Release Notes for V20.9
- Release Notes for V20.10
- Release Notes for V20.11
- Release Notes for V20.12
- Release Notes for V20.13
- Release Notes for V20.14
- Release Notes for V20.15
- Release Notes for V20.16
- Release Notes for V20.17
- Show all articles2 Collapse Articles
-
- Release Notes for V19.1
- Release Notes for V19.2
- Release Notes for V19.3
- Release Notes for V19.4
- Release Notes for V19.5
- Release Notes for V19.6
- Release Notes for V19.7
- Release Notes for V19.8
- Release Notes for V19.9
- Release Notes for V19.10
- Release Notes for V19.11
- Release Notes for V19.12
- Release Notes for V19.13
- Release Notes for V19.14
- Release Notes for V19.15
- Release Notes for V19.16
- Release Notes for V19.17
- Show all articles2 Collapse Articles
-
-
-
CDP – Customer Data Platform
-
-
- Personalization Overview
- Personalization - FAQs
- Personalization - Reporting
- Personalization - Archiving & Restoring
- Personalization - HTML Templates
- Personalization - Scroll Trigger and Infinite Scroll Pages
- Personalization - Merge Variables
- Personalization - 'Generate Personalization' Option
- Personalization & Metering - Click Tracking
- GDPR Consent Management
- Personalization - A/B Testing
-
-
Integrations
-
-
- Integration with Zapier
- Bring Customer Data in via Webhooks by Zapier Action - POST Event
- Bring Customer Data in using Zapier
- Omeda's Add Customer Action in Zapier
- Send Form Submission Data via Zapier
- Bring Customer Data in via Webhooks by Zapier Action – Custom Request Event
- Formatter by Zapier Action
-
-
-
Analytics & Reporting
-
- Odyssey - Reporting
- Personalization - Reporting
- Reports - Email Device and Client Type Reporting
- Email - Clickbot Reporting
- Reports - Email Reporting
- Metering - Reporting
- Reports - Audience Overlap Report
- Reports - Engaged Companies Report
- Reports-AutoRenewals Analysis Report
- Reports - Audience Report
- Reports - Issue Activity Reporting
- Reports - Overview
- Reports - Web Behavior Reporting
- Reports- FAQs
- Reports - Data Tracker Reporting
- Reports - Audience Builder Reporting
- Form Submit Report
- Behavior Promo Code Report
- Reporting Library
- Show all articles4 Collapse Articles
-
Marketing Automation & Email Builder
-
-
- Email On Demand Send
- Email Deployment
- Email Deployment Clone
- Email Deployment Remove Audience
- Email Audience Assignment Status
- Email Deployment Content
- Email Deployment Approval Lookup
- Email Deployment Schedule
- Email Deployment Cancel
- Email Deployment Search
- Email Flag Email As Invalid
- Email Clicks
- Email - Checklist for Sends Created via API Calls
- Email Deployment Lookup
- Email Deployment Test
- Email Deployment Add Audience
- Email Opt In/Out Lookup
- Email Optout Queue
- Email Optin Queue
- Email Deployment Audience List FTP
- Show all articles5 Collapse Articles
- Email Builder - User Guide
- Email - Clickbot Reporting
- Reports - Email Reporting
- Email - Link Tracking Errors
- Email - Deployment Defaults
- Omeda - Getting Support
- Email - Checklist for Sends Created via API Calls
- Email - Assigning Link Tracking Categories
- Email - Deliverability
- Email - Opt-Out Footer Merge Variable
- Email - Stealth Link
- Email - Behavioral Data
- Email - Automation for Email Sending
- Email - Deployment Type Creation
- Email – Training Schedules for New Clients
- Email - Request a New Deployment Type
- Email - Adding Domains to Safe Sender List
- Email - Deployment Checklist & Best Practices
- Email Deployment Unschedule
- Email Builder - Getting Started
- Campaign Tool - Overview
- Email - Automated ACS Notifications
- Email - Dynamic Content
- Email - Recurring Deployments
- Email - FAQs
- Email - Web Tracking
- Email - Validation Services
- Email Services - Overview & Capabilities
- Email - Web Tracking String Parameter Definitions
- Email - Appending Lists On Triggered Deployments
- Email - Preference Page
- Email - A/B Testing
- Email - Triggered Deployments
- Email - Merge Variables
- Email - User Set-up
- Email - Advanced Features
- Email - Glossary
- Email – Checklist for New Clients
- Show all articles23 Collapse Articles
-
-
-
- Odyssey - Audience Element
- Odyssey - Timing Elements
- Odyssey - Adroll Elements
- Odyssey - Facebook Elements
- Odyssey - Filter Element
- Odyssey - Form Submit Element
- Odyssey - Pathfinder Element
- Odyssey - Export Element
- Odyssey - Split Element
- Odyssey - Personalization Element
- Odyssey - Metering Element
- Odyssey - Email Element
- Odyssey - Goal Element
- Odyssey - A/B Test Element
- Odyssey - Google Ad Manager Element
- Odyssey Fatigue Filter Element
- Show all articles1 Collapse Articles
- Odyssey Overview
- Odyssey - FAQs
- Odyssey - Editing an In Progress Voyage
- Odyssey - Reporting
- Odyssey - Querying Element Visitors in Audience Builder
- Odyssey - Using Profiles
- Odyssey - Creating Custom Templates
- Odyssey - Global Settings
- Odyssey - Email Conditions
- Odyssey - Omeda's Email Designer
- Odyssey - Email Designer Templates
- Odyssey - Voyage Templates
- Odyssey - Merging Paths
- Odyssey - Email Merge Variables
- Odyssey - Error Troubleshooting
- Odyssey - Dynamic Content
- Show all articles1 Collapse Articles
-
-
-
Data Management & Governance
-
- Odyssey - Querying Element Visitors in Audience Builder
- Audience Builder - Product Field Library
- Examples of Audience Builder Queries Using Paid Fields
- Querying Your Olytics Data
- Data Loader - Querying in Audience Builder
- Email - Behavioral Data
- Audience Builder (OnQ) - Date Field Definitions
- Audience Builder - How To Query Customers
- Audience Builder (OnQ) - Query Result Outputs
- Audience Builder - Overview
- Reports - Audience Builder Reporting
- Audience Builder - Admin User Guide
- Audience Builder (OnQ) - Advanced Features
- Audience Builder (OnQ) - Match Evaluation
-
- Client Empowerment: Message Types
- Client Empowerment: Profiles
- Client Empowerment: API Keys
- Client Empowerment: Alternate IDs
- Client Empowerment: Logos
- Client Empowerment: Demographics
- Client Empowerment: Database Settings
- Client Empowerment: Behaviors
- Client Empowerment: Deployment Products
- Client Empowerment: Deployment Types
- Client Empowerment : Managing Your Database
-
-
Subscription & Fulfillment Management
-
Forms & Landing Pages
-
- Form Builder Overview
- Form Builder - Form Dashboard
- Form Builder - Content
- Form Builder - Integrations
- Form Builder - Expressions
- Form Builder - Create a Form
- Form Builder - Settings
- Form Builder - Form Categories and Form Types
- Form Builder - Builder
- Form Builder - Error Log
- Form Builder - Payment Gateways
- Form Builder ADA Compliance
-
- How to send a user back to your website after form submission (redirect to a return URL)
- Form Builder - Adding a This Is Not Me Widget
- Form Builder - Embedding Webforms via iFrame or Javascript
- How To Use Progressive Profiling
- Form Builder - Using the PayPal Payment Method
- Form Builder - Using Campaign Promo Codes
- Using Form Builder to capture a Behavior Subscription Attribute
- Form Builder - reCAPTCHA v3 Implementation
- How To Use A/B Testing on your Form Builder Webform (video)
- Styling Your Form Builder Forms
- Best Practices for Testing Forms
- Form Builder Forms URL Structure and Appending Parameters
- Using a Custom Domain for your Form Builder Webform
-
-
Success Use Cases
-
Professional Services
-
Video Library
-
FAQs
Reports – Data Tracker Reporting
Overview
The Data Tracker Report is a report you may refer to when you want to view the activity of data batches as it is processed through Datapool and onto the Omeda Database. From beginning to end, you will be able to see when your entries get processed, how many are successful, how many have to be reconciled and how any new entries affect your current customer records previously processed.
Running the Data Tracker Report
You need to be given access to this report by your Client Services Manager. To run the report,
- Go to the Reports tab.
- In the Data Reports section, click on Data Tracker Report. Select your report parameters:
- Required field: Client, Brand, Product, Sources, Date Range (Input is required for internal Omeda users only)
- Prep Date: The date the mailed customer records were initially scanned & sent for keying.
- Processed Date: The date the first customer record in the batch was processed from Datapool into the Omeda Database.
- Optional fields: Promo Codes, Batch, Error Codes
- Required field: Client, Brand, Product, Sources, Date Range (Input is required for internal Omeda users only)
- Click Generate Report in the upper right corner.
Data Tracker Report Fields
The Data Tracker Report is an excellent resource when wanting to view the status & success of one or multiple batches from start to finish. In it, you will find three buckets – “Batch Description,” “Processor Status” and “Successfully Processed Records.”
Under “Batch Description,” you will see the exact number of customer records sent in each batch, input method, source, number of returned customer records, Datapool entry date and processed date. Under “Processor Status,” you will see in more detail the number of customer records that are ready to process in each batch, if any additional mapping is necessary, how many customer records failed and how many were successfully processed. Lastly, within “Successfully Processed Records,” you will be able to view the number of qualified and non-qualified customer records for new additions and updates as well as customer records that are already classified as 1 year.
![](https://training.omeda.com/wp-content/uploads/2021/09/Batch-Description.png)
Batch Description
- Input: This field lists the input value being reviewed.
- Source: The source field reflects where the data came from (e.g., Request from Company – Written, Direct Request – Telecom, etc.).
- Batch Tracking Code: This field specifies which customer records batch the data is for. Each batch ID is unique.
- Note: All Web Batch Tracking Codes for a given day will be rolled up into one line.
- Vendor File Name: The vendor’s file name now appears in the Data Tracker report for files from external sources. This will allow you to easily balance the files that you receive from external sources.
- Sent: This field reflects the total number of processed and unprocessed customer records sent for keying.
- Returned: This field reflects the total number of customer records keyed and ready for processing.
- Balance: The number of customer records not sent back to Omeda from the key house.
- Prep Date: The date the mailed customer records were initially scanned & sent for keying. Neither Internet nor phoned customer records will have a prep date.
- Datapool Date: The date the first customer records were placed into Datapool.
- Processed Date: The date the first customer record in the batch was processed from Datapool into the Omeda Database.
Processor Status
- Data within Processor Status (except for the Loaded into Datapool column) is equivalent to the Sent column under Batch Description
- Loaded into Datapool: The number of customer records loaded into Datapool on the date specified under Datapool Date that are awaiting processing.
- Failed Validation Rules: The number of customer records that contained an error or did not include required information (e.g. ZIP code and state didn’t match, missing name, missing PID, suspected vulgarity, etc.).
- Open Ended Coding: The number of customer records that require additional mapping before the record(s) may be processed (e.g. a customer who selects an “other” field and needs to be mapped to another valid category).
- Failed Source Priority: If the record has already been inputted into the Omeda Database on a prior date with a more reliable source, the new source may or may not be rejected based on pre-defined source priority rules. Note: this field is commonly only attributed to non-paid/controlled records.
- Ready to Process: The number of customer records ready to be processed into the Omeda Database.
- Discarded: The number of entries Omeda is not able to input. These entries are not able to be processed and will remain in Datapool.
- Partially Processed: If a record has all required information but only missing optional fields or has a failed prioritization source, these entries will still be processed partially and be reflected in this field.
- Successfully Processed
- New: The number of new records successfully processed to the database resulting in a new customer record being created.
- Existing: The number of existing customer records successfully updated and processed within the database.
Successfully Processed Records
Note: All fields (except “Other”) within Successful Processed Reports are split by “Qualified” or “Non-Qualified.” Qualified customer records are those in which are qualified subscribers (class 1 or 3). Non-Qualified customer records are those which are not qualified subscribers (expired, suspended, killed, payment pending, etc.).
- Adds and Updates/renewals is equivalent to the sum of New and Existing under Successfully Processed in the Processor Status section
- Adds: The number of new qualified and non-qualified customer records that passed all Datapool checks and have been successfully processed.
- Updates/Renewals: The number of updated or renewed qualified and non-qualified customer records that passed all Datapool checks and have been successfully processed.
- Updated Already 1 Year: The number of customer records that have already been updated within the past audit cycle year. The record will be added but counted as already 1 year.
- Example: Product A: 1 year start date is 1 Dec 2012, which means audit cycle period is 1 Dec 2012 – 30 Nov 2013.
- Scenario #1: I have a subscription to that product with a verifdate of 1 June 2012. I am a “2yr” record because my verfidate (1 June 2012) is before the start date (1 Dec 2012). I submit a new order with a verifdate of 1 Jan 2013. I become a 1 year record. I am counted as a renewal. I am not counted as an already 1 year renewal.
- Scenario #2: I have a subscription to that product with a verifdate of 2 Dec 2012. I am a “1yr” record because my verifdate (2 Dec 2012) is > start date ( 1 Dec 2012). I submit a new order with a verifdate of 1 Jan 2013. I am counted as an “already 1yr renewal.”
- Example: Product A: 1 year start date is 1 Dec 2012, which means audit cycle period is 1 Dec 2012 – 30 Nov 2013.
- Other: This field reflects the number of non-magazine products that have been successfully processed in Datapool. This field does not have “Qualified” or “Non-Qualified” sub-fields.
- Updates/Renewals Minus Updates Already 1 Year: The number of customer records in the batch that resulted in either new records being created, or existing records being upgraded to a better source/recency.
- Formula: adds + (update/renewal – updates a already 1 year) = updates/renewal minus updates already 1 year
![](https://training.omeda.com/wp-content/uploads/2021/09/successfully_processed-data-tracker.png)
![](https://training.omeda.com/wp-content/uploads/2021/09/updates-renewals-small-data-tracker.png)