Cloud Connector extension overview
The Cloud Connector event forwarding extension allows you to create custom HTTP requests to send data to a destination or retrieve data from a destination. The Cloud Connector extension is like having Postman on Adobe Experience Platform Edge Network and can be used to send data to an endpoint that does not have a dedicated extension yet.
Use this reference for information about the options available when using this extension to build a rule.
Cloud Connector extension action type
This section describes the Send Data action type available in the Adobe Experience Platform Cloud Connector extension.
Request type
To select the type of request required by the endpoint, select the appropriate type under the Request Type dropdown.
Endpoint URL
In the text field next to the Request type dropdown menu, enter the URL for the endpoint to which you are sending data.
Query params, headers, and body configuration
Use each of these tabs (Query Params, Headers, and Body Data Elements) to control what data is sent to a given endpoint.
Query Params
Define a key and value for each key-value pair you want to send as a query string parameter. To manually enter a data element, use the curly brace data element tokenization for event forwarding. To reference the value of a data element named “siteSection” as a key or value, enter {{siteSection}}
. Or, select the previously-created data element by selecting it in the dropdown menu.
To add more query parameters, select Add Another.
Headers
Define a key and value for each key-value pair you want to send as a header. To manually enter a data element, use the curly brace data element tokenization for event forwarding. To reference the value of a data element named “pageName” as a key or value, enter {{pageName}}
. Or, select the previously created data element by selecting it in the dropdown menu.
To add more headers, select Add Another.
The following table lists the predefined headers. You are not limited to these headers and can add your own custom headers if required, but they are made available for your convenience.
Accept-Datetime
header is conveyed in an HTTP request issued against a TimeGate for an original resource, and its value indicates the datetime of the desired past state of the original resource.Set-Cookie
header.Accept-Transfer-Encoding
, which would be more intuitive).Upgrade
header field is RFC 7230, section 6.7. The standard establishes rules for upgrading or changing to a different protocol on the current client, server, transport protocol connection. For example, this header standard allows a client to change from HTTP 1.1 to HTTP 2.0, assuming the server decides to acknowledge and implement the Upgrade
header field. Neither party is required to accept the terms specified in the Upgrade
header field. It can be used in both client and server headers. If the Upgrade
header field is specified, then the sender MUST also send the Connection
header field with the upgrade
option specified.Body as JSON
Define a key and value for each key-value pair you want to send in the body of the request. To manually enter a data element, use the curly brace data element tokenization for event forwarding. To reference the value of a data element named “appSection” as a key or value, enter {{appSection}}
. Or, select the previously-created data element by selecting it in the dropdown menu.
To add additional key-value pairs, select Add Another.
Body as Raw
Define a key and value for each key-value pair you want to send in the body of the request. To manually enter a data element, use the curly brace data element tokenization for event forwarding. To reference the value of a data element named “appSection” as a key or value, enter {{appSection}}
. Or, select the previously created data element by selecting it in the dropdown menu. You can add one or more data elements.
Advanced
Actions within rules in event forwarding execute sequentially. There could be situations where you want to retrieve data from an external source that is not present on the incoming event from the client and then take this response and either transform or send this data to a final destination in a subsequent action within a single rule. The “Save the request response” in the advanced section enables this.
To save the response body from an endpoint check the Save the request response box and define a response key in the text field.
If you defined the response key as productDetails
, reference this data in a data element and then reference this data element in a subsequent action within the same rule. To create a data element that references productDetail
, create a data element of type path
and enter the following path:
arc.ruleStash.[EXTENSION-NAME-HERE].responses.[RESPONSE-KEY-HERE]
arc.ruleStash.adobe-cloud-connector.reponses.productDetails