sfmc-customevent-with-transactionkey | Salesforce Marketing Cloud - Custom Event
kandi X-RAY | sfmc-customevent-with-transactionkey Summary
kandi X-RAY | sfmc-customevent-with-transactionkey Summary
sfmc-customevent-with-transactionkey is a JavaScript library. sfmc-customevent-with-transactionkey has no bugs, it has no vulnerabilities, it has a Permissive License and it has low support. You can download it from GitHub.
This is a basic example for a custom entry event that allows creating unique journey results using transaction keys as mentioned in the marketing cloud documentation under Journey Settings and Create Unique Journey Results using Transaction Keys.
This is a basic example for a custom entry event that allows creating unique journey results using transaction keys as mentioned in the marketing cloud documentation under Journey Settings and Create Unique Journey Results using Transaction Keys.
Support
Quality
Security
License
Reuse
Support
sfmc-customevent-with-transactionkey has a low active ecosystem.
It has 7 star(s) with 8 fork(s). There are 3 watchers for this library.
It had no major release in the last 6 months.
sfmc-customevent-with-transactionkey has no issues reported. There are no pull requests.
It has a neutral sentiment in the developer community.
The latest version of sfmc-customevent-with-transactionkey is current.
Quality
sfmc-customevent-with-transactionkey has 0 bugs and 0 code smells.
Security
sfmc-customevent-with-transactionkey has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.
sfmc-customevent-with-transactionkey code analysis shows 0 unresolved vulnerabilities.
There are 0 security hotspots that need review.
License
sfmc-customevent-with-transactionkey is licensed under the MIT License. This license is Permissive.
Permissive licenses have the least restrictions, and you can use them in most projects.
Reuse
sfmc-customevent-with-transactionkey releases are not available. You will need to build from source code and install.
Installation instructions are available. Examples and code snippets are not available.
It has 66 lines of code, 0 functions and 4 files.
It has low code complexity. Code complexity directly impacts maintainability of the code.
Top functions reviewed by kandi - BETA
kandi has reviewed sfmc-customevent-with-transactionkey and discovered the below as its top functions. This is intended to give you an instant insight into sfmc-customevent-with-transactionkey implemented functionality, and help decide if they suit your requirements.
- Save the data to the step .
- simple ready event listeners
- Helper for creating an object .
- Convert the i . e into a string
- Iterates over all properties of an object .
- Mix one object into another
- wrap a function
- Return all script tags
- Default error handling .
- Get the global name of a global object .
Get all kandi verified functions for this library.
sfmc-customevent-with-transactionkey Key Features
No Key Features are available at this moment for sfmc-customevent-with-transactionkey.
sfmc-customevent-with-transactionkey Examples and Code Snippets
No Code Snippets are available at this moment for sfmc-customevent-with-transactionkey.
Community Discussions
No Community Discussions are available at this moment for sfmc-customevent-with-transactionkey.Refer to stack overflow page for discussions.
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install sfmc-customevent-with-transactionkey
Before this example can be used, a package containing a Journey Builder Trigger needs to be created in Salesforce Marketing Cloud App Center. A documentation for this task can be found here: Create a Marketing Cloud App. Important: The trigger's "Public Extension"-setting needs to be set to "This application and other installed Applications" and the example needs to be available via HTTPS which has to be running on the default port 443.
The unique key of the created Journey Builder Trigger needs to be added to config.json properties key and configurationArguments.applicationExtensionKey
Optional: An icon for the custom event can be added to config.json under metaData.icon (which isn't present in the example)
The unique key of the created Journey Builder Trigger needs to be added to config.json properties key and configurationArguments.applicationExtensionKey
Optional: An icon for the custom event can be added to config.json under metaData.icon (which isn't present in the example)
Support
For any new features, suggestions and bugs create an issue on GitHub.
If you have any questions check and ask questions on community page Stack Overflow .
Find more information at:
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page