npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

sparkpost-recipient-filter

v1.0.0

Published

Filters a SparkPost recipient list by recipient attributes

Downloads

5

Readme

sparkpost-recipient-filter

Build Status Coverage Status

Filters a SparkPost recipient list by domains, tags, metadata and/or substitution data.

Disclaimer

SparkPost is not a replacement for a marketing tool, if you need advanced subsetting of recipients for your messaging, consider an Email Service Provider.

Usage

This library exposes a filter method that returns a promise resolved with an array of recipient objects who match the given criteria.

Your SparkPost API key will need Recipient Lists: Read/Write permissions.

NOTE: Works in Node v4.0.0 and up.

let recipientFilter = require('sparkpost-recipient-filter')(process.env.SPARKPOST_API_KEY);

recipientFilter.filter('myListId', {
  domain: 'gmail.com',
  tags: ['super', 'cool'],
  metadata: {place: 'New York City'},
  substitution_data: {language: 'javascript'}
}).then(recipients => {
  // recipients is an array of SparkPost recipient objects
});

Filtering

If multiple criteria are passed in the filter config, the match is performed using AND logic. So if you pass both tags and a domain, only recipients with the given tags and at the given domain will be returned.

Matching Tags

If a tags array is passed, all recipients who have all matching tags will be returned. This is a strict subset match, so recipients must have all tags that are passed in the filter config but may have more.

Example:

// will find users with tags ['one', 'two'] but not ['one']
require('sparkpost-recipient-filter')(process.env.SPARKPOST_API_KEY)
  .filter('myListId', {tags: ['one', 'two']})
  .then(list => console.log(list))
  .catch(err => console.log(err));

Matching Domain

If a domain is passed, returns recipients with the given email address domain.

Example:

// will find users with @gmail.com email addresses
require('sparkpost-recipient-filter')(process.env.SPARKPOST_API_KEY)
  .filter('myListId', {domain: 'gmail.com'})
  .then(list => console.log(list))
  .catch(err => console.log(err));

Matching Metadata and Substitution Data

Matches recipients who have the passed metadata and/or substituition_data. This is a strict subset match, so recipients must have all values that are passed in, but may have more.

Array properties must have exactly the same elements in order to match.

Metadata example:

// will find users with a location.city value of "NYC" AND a location.borough value of "Brooklyn"
require('sparkpost-recipient-filter')(process.env.SPARKPOST_API_KEY)
  .filter('myListId', {
    metadata: {
      location: {
        city: 'NYC',
        borough: 'Brooklyn'
      }
    }
  })
  .then(list => console.log(list))
  .catch(err => console.log(err));

Substitution data example:

// will find users with a location.city value of "NYC" AND a locaiont.borough value of "Brooklyn"
require('sparkpost-recipient-filter')(process.env.SPARKPOST_API_KEY)
  .filter('myListId', {
    substitution_data: {
      location: {
        city: 'NYC',
        borough: 'Brooklyn'
      }
    }
  })
  .then(list => console.log(list))
  .catch(err => console.log(err));