v3.3.3

Fixed

• Use the track api url instead of the app api url for mergeCustomers (#114)

v3.3.2

Changed

• Add more files to the npm ignore file (#109)
• Attempt to re-publish to get a proper build before publishing

v3.3.1

Changed

• Export CustomerIORequestError in Typescript types (#108)

v3.3.0

Added

• Added support for use with gitpod (#101)
• Added support for invite-type anonymous event tracking (#106, #107)

Updated

• Export more types from request.ts (#102)

Fixed

• Fix instances of customerio-node running without a package.json alongside the code (#105)

v3.2.0

• Add support for push metrics tracking endpoint (#98)

v3.1.4

• Add send_at to transactional message attributes (#97)
• Set User-Agent for proper source attributes on activity logs (#96)

Revert `User-Agent` changes

Fixes

• Revert #93 due to a crashing bug (#95)

Add `User-Agent` header to request headers to Customer.io

Fixes

• Set User-Agent for property source attributes on activity logs #93

Fix types for transactional messages

Fixes

• Fixed types for the fake_bcc parameter for transactional emails #92

Support for merge customers API

When you merge two people, you pick a primary person and merge a secondary, duplicate person into it. The primary person remains after the merge and the secondary is deleted. This process is permanent: you cannot recover the secondary person.

The first and third parameters represent the identifier for the primary and secondary people respectively—one of id, email, or cio_id. The second and fourth parameters are the identifier values for the primary and secondary people, respectively.

More details in API Documentation