Triggers the sending of a campaign. When sending a campaign it will either start the campaign immediately or queue it for sending if it is currently outside of timezone protection. Be aware that queueing multiple messages to send at the very beginning of timezone protection may run into queueing issues if there is insufficient capacity.
We recommend sending based on a contactId. If not provided, then a Contact will be created based upon the extData provided.
In the event of a conflict either the behavior depends on the conflictMode (default OVERWRITE) to either REJECT, OVERWRITE, or APPEND extData and keys for the existing contact.
If creating a new contact extData is required. keys is highly recommended, though some of these will be generated from extData. Refer to the Contacts section for more details.
For data that is relevant only to the campaign campaignExtData should be used. When evaluating a campaign, the campaignExtData is used preferentially over the extData stored on the contact.
