Security News
The Unpaid Backbone of Open Source: Solo Maintainers Face Increasing Security Demands
Solo open source maintainers face burnout and security challenges, with 60% unpaid and 60% considering quitting.
react-native-customerio
Advanced tools
A react-native for the Customer.io event API. http://customer.io
A react-native client for the Customer.io REST API.
This project was initally forked from https://github.com/customerio/customerio-node
npm i --save react-native-customerio
In order to start using the library, you first need to create an instance of the CIO class:
let CIO = require('react-native-customerio');
const cio = new CIO(siteId, apiKey, [defaults]);
Both the siteId
and apiKey
are required in order to create a Basic Authorization header, allowing us to associate the data with your account.
Optionally you may pass defaults
as an object that will be passed to the underlying request instance. A list of the possible options are listed here.
This is useful to override the default 10s timeout. Example:
const cio = new CIO(123, 'abc', {
timeout: 5000
});
Creating a person is as simple as identifying them with this call. You can also use this method to update a persons data.
cio.identify(1, {
email: 'customer@example.com',
created_at: 1361205308,
first_name: 'Bob',
plan: 'basic'
});
This will delete a person from Customer.io.
cio.destroy(1);
The track method will trigger events within Customer.io. When sending data along with your event, it is required to send a name key/value pair in you data object.
Simple event tracking
cio.track(1, { name: 'updated' });
Sending data with an event
cio.track(1, {
name: 'purchase',
data: {
price: '23.45',
product: 'socks'
}
});
Anonymous event tracking does not require a customer ID and these events will not be associated with a tracked profile in Customer.io
cio.trackAnonymous({
name: 'updated',
data: {
updated: true,
plan: 'free'
}
});
Sending a page event includes sending over the customers id and the name of the page.
cio.trackPageView(1, '/home');
Trigger an email broadcast using the email campaign's id. You can also optionally pass along custom data that will be merged with the liquid template, and additional conditions to filter recipients.
cio.triggerBroadcast(1, { name: 'foo'}, { segment: { id: 7 }});
You can also use emails or ids to select recipients, and pass optional API parameters such as email_ignore_missing
.
cio.triggerBroadcast(1, { name: 'foo'}, { emails: ['example@emails.com'], email_ignore_missing: true }
);
You can learn more about the recipient fields available here.
Add a device to send push notifications.
cio.addDevice(1, "device_id", "ios", { primary: true });
Delete a device to remove it from the associated customer and stop sending push notifications to it.
cio.deleteDevice(1, "device_token")
Suppress a customer.
cio.suppress(1)
All calls to the library will return a native promise, allowing you to chain calls as such:
const customerId = 1;
cio.identify(customerId, { first_name: 'Finn' }).then(() => {
return cio.track(customerId, {
name: 'updated',
data: {
updated: true,
plan: 'free'
}
});
});
To use the Customer.io Transactional API, import our API client and initialize it with an app key.
Create a new SendEmailRequest
object containing:
transactional_message_id
: the ID of the transactional message you want to send, or the body
, from
, and subject
of a new message.to
: the email address of your recipientsidentifiers
object containing the id
of your recipient. If the id
does not exist, Customer.io will create it.message_data
object containing properties that you want reference in your message using Liquid.attach
to encode attachments.Use sendEmail
referencing your request to send a transactional message. Learn more about transactional messages and SendEmailRequest
properties.
const { APIClient, SendEmailRequest } = require("react-native-customerio/api");
const client = new APIClient("your API key");
const request = new SendEmailRequest({
to: "person@example.com",
transactional_message_id: "3",
message_data: {
name: "Person",
items: {
name: "shoes",
price: "59.99",
},
products: [],
},
identifiers: {
id: "2",
},
});
// (optional) attach a file to your message.
request.attach("receipt.pdf", fs.readFileSync("receipt.pdf"));
client.sendEmail(request)
.then(res => console.log(res))
.catch(err => console.log(err.statusCode, err.message))
We've included functional examples in the examples/ directory of the repo to further assist in demonstrating how to use this library to integrate with Customer.io
npm install && npm test
Released under the MIT license. See file LICENSE for more details.
FAQs
A react-native for the Customer.io event API. http://customer.io
The npm package react-native-customerio receives a total of 24 weekly downloads. As such, react-native-customerio popularity was classified as not popular.
We found that react-native-customerio demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Solo open source maintainers face burnout and security challenges, with 60% unpaid and 60% considering quitting.
Security News
License exceptions modify the terms of open source licenses, impacting how software can be used, modified, and distributed. Developers should be aware of the legal implications of these exceptions.
Security News
A developer is accusing Tencent of violating the GPL by modifying a Python utility and changing its license to BSD, highlighting the importance of copyleft compliance.