Can Emma's API list members by status and date range?

  • 0
  • 1
  • Question
  • Updated 4 years ago
  • Answered
Photo of Social Media Mentions

Social Media Mentions

  • 39 Posts
  • 0 Reply Likes

Posted 4 years ago

  • 0
  • 1
Photo of Katie Lewis

Katie Lewis, Official Rep

  • 3414 Posts
  • 309 Reply Likes
Hi Derek! I just spotted on Twitter that you may have gotten this sorted out. Are you all set? What steps did you take to get the results you expected?
Photo of COLE Publishing Inc

COLE Publishing Inc

  • 5 Posts
  • 0 Reply Likes
oh, hey, that's my tweet. i've got this specific issue worked out using the custom search API.

http://api.myemma.com/api/external/searches.html

or at least i think i do. but now i'm questioning some of my assumptions. the specific context here is i run an in house CRM system for a niche B2B publisher. one of the potential data points stored in this system is email addresses provided by our print subscribers. but it is essentially just a dumb data store. it doesn't know anything about those email addresses beyond the customer profile it is associated with, when it was added to the system, and that it appears to be well formed. 

we've been heavy emma users since...2005 or so. so emma has a lot of meta data for the majority of the email addresses in the CRM system. the most obvious use for the API would be to purge known undeliverable addresses. and i'm attempting to write a cron job to do just that. i have a feeling there are tons of opportunities to pursue with the API so this is partially just an excuse to wrap my head around it more fully.

i'll list my current assumptions:

  1. a status of e / error marks a member as effectively undeliverable, at least within the context of my purposes.
  2. once a member falls into the error status they tend to remain there indefinitely. 
  3. there are few reasons to modify a member record once it falls into an error state.
those assumptions lead me to create a custom search to query for members with an error status whose last_modified_at attribute is within the past week. those are returning results along the lines of what i expect. the execution time for each API call (we have multiple accounts with a custom search end point for each) averages around 15 seconds. that seems oddly slow, but since the end game here is a cron job that will run once a week i am not that concerned about it. everything is built, tested, and working in development. but before i roll it out to production i'd like to confirm my assumptions above hold true. 

if an error status can represent things other than being effectively undeliverable then my current data model won't fit reality. if members may fall into an error state only temporarily then i need to provide another set of API based methods for double checking the status of members previously marked as in an error state. if the modified timestamps are routinely updated on members who are already in an error state then my API results will contain lots of false positives. that last one isn't a deal breaker because updating the internal status to error when it is already at error does no harm. it just feels inefficient. 

if thorough documentation on the life cycle of a member profile with particular attention paid to what exactly an error status means is available at some as of yet undiscovered URL that would likely answer all my nagging insecurities. ;) 
Photo of Katie Lewis

Katie Lewis, Official Rep

  • 3414 Posts
  • 309 Reply Likes
Hey Derek! You're right that people who are in Error status cannot be sent to. When you send a mailing to a group/segment, you're only sending to the Active contacts in a group/segment. Contacts are typically in Error due to past delivery problems, and they won't move back to Active status unless you take action to change their status.

There are also typically few reasons to move someone from Error to Active. In the Error to active section on this page of our Resource Center, a couple examples are given of times you might need to change someone's status.

I'm sorry that those help docs are tough to find! You have an agency account, so your Help link currently points to another URL. I manage the help docs, and we're in the process of getting all accounts to using the same Resource Center. We're sensitive to the need of some agencies to not include Emma branding in their help docs, so we're working to private-label the pages for agencies. I'm hopeful you'll have access to these comprehensive pages in an easier-to-find way in the next few quarters. :)
Photo of COLE Publishing Inc

COLE Publishing Inc

  • 5 Posts
  • 0 Reply Likes
we're in house, but we cover several different brands. that's probably why we are set up like an agency. and again, we've been with emma for a decade or so. i'm not sure what account structures existed when we signed up, how they may have changed, or who made the decisions at the time. :)

the API docs were easy enough to find and navigate. the screen shot of where to find the API keys within an account may be a bit stale. it doesn't match what i see within our dashboard. but the general "go here, look for this" type info was still useful. i can't complain. 

but the entire support.myemma.com subdomain has escaped me through all my googling and clicking around within our account. that looks like exactly what i've been looking for. and it sounds like all my assumptions hold water. 

thanks for the quick reply. :)
Photo of Katie Lewis

Katie Lewis, Official Rep

  • 3414 Posts
  • 309 Reply Likes
Awesome, glad you're all set! Yep, I noticed that you have a very low account number, so I could tell you've been around for a minute. :)

I've let our API folks know about the screenshot. It's from a direct account, so your setup will look a bit different. I'm hopeful we can include an example of what an agency like yours will see.