update version number and publish new version to NPM
Also update README to show the version change.

postParam should equal "reportSuiteID" in index.js

The library currently makes pageName mandatory. However, as the XML API spec states:

to specify that a given row should be considered a page view, that row must contain either pageName or pageURL. To specify that a given row should be considered a link event, that row must include linkType and either linkName or linkURL. If a given row contains both linkType and either pageName or pageURL, Adobe Analytics will automatically clear out pageName and pageURL by setting them to null.

We are using the library purely for link event tracking, so we don't need to pass pageView and yet the library forces us. As it is if we somehow end up with an accidentally undefined linkName the lib will fall back to using the pageName value.

The validation should be smart enough to handle these scenarios.

Thanks for pulling in #6!
Is it possible to bump the patch version 1.0.5 (or even a minor version 1.1.0 since it has a new feature), and publish to npm?

Thanks!

This code enforces that either ip or visitor is defined and throws an error if both are undefined.

This is incorrect. As per the AA docs, marketingCloudVisitorID is a valid visitor identification method.

Errors should not be thrown if the marketingCloudVisitorID is defined.

I would like to send a PR for this feature, but discussing it here first.

We are using this library in a command line context, so we need to suppress any console.* calls. I'm thinking of either overriding this call with an extra boolean parameter (to suppress), or optionally pass in an object that is to be used instead of console (this object will have log and error as exported functions).

The intent of this change would be that the existing behaviour will not change if that extra parameter is not set. What do you think?

This library uses xyz.112.2o7.net as the default collection server (as opposed to xzy.sc.omtrdc.net), which means it's using the old configuration and is not Regional Data Collection (RDC) enabled. Sure, this can be overridden using the "setTrackingServerUrl" method to use an RDC endpoint, but sensible defaults should be used, rather than old legacy defaults.

There are many customers who had not transitioned to RDC, but wanted to implement server-side-forwarding using server-side Adobe Analytics. They had a lot of problems with it, especially, many unsuccessful calls. They transitioned to RDC and all these problems went away.

As it stands, the contextData property forces the developer to provide values as XML, like this:

var callData = { pageName: 'analytics-di-test', visitorID: 'myvisitorId123123123123', contextData: '<sc_contextDataTest>my context data test</sc_contextDataTest>' };

It is very confusing for a Node library to ask developers to provide XML strings. JSON is the object notation for JavaScript and it should be the library's job to convert a developer's context data JSON object into the required XML string that the AA API expects, instead of putting this burden on the developer.

At the moment, the docs link to a dead page https://marketing.adobe.com/developer/documentation/data-insertion/c-data-insertion-api

This should instead link to the DI XML spec:
https://github.com/AdobeDocs/analytics-1.4-apis/blob/master/docs/data-insertion-api/index.md

will this work in angular 7?