Skip to content

Commit 65ce2a3

Browse files
Fix typo in image filename
1 parent a5eeb5f commit 65ce2a3

File tree

1 file changed

+1
-1
lines changed
  • src/connections/destinations/catalog/actions-stackadapt

1 file changed

+1
-1
lines changed

src/connections/destinations/catalog/actions-stackadapt/index.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -156,7 +156,7 @@ This is necessary when using backend SDKs but not for events sent from the front
156156

157157
When sending past events to StackAdapt using a Reverse ETL tool, the user agent, IP address, event type, and either the page URL (for conversion trackers with URL rules), or the fields the event rules match on, must be included in your mappings. For example, the below mapping for a Snowflake source can be used to match a conversion tracker with an event rule that matches an `action` of `User Registered`:
158158

159-
![Image showing Snowflake mapping to forward User Registered events](images/snowflake-mapping.png)
159+
![Image showing Snowflake mapping to forward User Registered events](images/snowflake-mappings.png)
160160

161161
Rows forwarded to StackAdapt with this mapping will be matched by the `User Registered` event rule shown below:
162162

0 commit comments

Comments
 (0)