Identify Records where Acquisition Date ≠ Created Date | Community
Skip to main content
keithnyberg
keithnyberg
Level 7
February 28, 2018
Question

Identify Records where Acquisition Date ≠ Created Date

  • February 28, 2018
  • 2 replies
  • 6974 views

Hey Community,

Anyone have any clever or easy ways to isolate records that have an acquisition date that doesn't match a creation date? I know I have some of these records in my database based on poor older practices and am working to reconcile.

I tried to create a smart list with the filter Acquisition Date ≠ Created At to isolate affected records, but this does not work as the {{lead.Created At}} token is invalid in the Acquisition date filter.

I know I can export my entire DB and audit the acquisition date relative to the creation date, but as my existing DB is nearly 700K people, this will take alot of time and my Macbook will probably crash trying to open the .xls.

Does anyone know of an easier way to isolate these records to correct inconsistencies in MKTO?

I know I can run my entire BD through a smart campaign to set Acquisition Date = Created At but again want to avoid touching all the records in my DB when my gut is only a few thousand are out of sync if any. (this would also majorly backlog my campaign queue)

Let me know what ya got and thanks in advance for reading/engaging in this community.

Sincerely,

Keith Nyberg

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

    2 replies

    J
    Community Advisor
    JDNelson1Community Advisor
    Community Advisor
    February 28, 2018

    what if you run a batch to copy acquisition date to a new string field, then you can compare those two fields?

    keithnyberg
    keithnybergAuthor
    Level 7
    February 28, 2018

    That is a great idea but still requires me to run my entire DB through the campaign to isolate the records which is really not ideal. If I'm gonna run my whole DB through a campaign, might as well just run Set Acquisition Date = Created Date. Same campaign run time....

    Dan_Stevens_
    Dan_Stevens_
    Level 10
    February 28, 2018

    Keith, also be aware that you can't use tokens in smart list filters/triggers.

    keithnyberg
    keithnybergAuthor
    Level 7
    February 28, 2018

    Yeah... that is the major problem here... not sure there is a better solution than just dumping my DB,  isolating records that are not equal and then importing the Created At date into the Acquisition Date field.

    Dan_Stevens_
    Dan_Stevens_
    Level 10
    February 28, 2018

    For us, having different AD and CD are normal.  Unless we’re importing people into a program that is part of a “list acquisition“ program, we don't assign AP/AD during the import process.  Mainly because the leads themselves didn't engaged with anything to qualify them as members of a program.  Which is why we also always include a flow step - in all of our programs - to define the AP within the first program they actively engage with.

    Terms & ConditionsAccessibility statement

    Loading footer...