You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: source/includes/_locations.md
+33-33Lines changed: 33 additions & 33 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -161,16 +161,16 @@ This element is positioned below the vehicle pricing area on vehicle search and
161
161
162
162
This element is the media gallery container on vehicle details pages. Injecting into this location will replace the media gallery with the elements you insert.
163
163
164
-
## Secondary Content
164
+
## Primary Banner
165
165
166
166
> Usage:
167
167
168
168
```javascript
169
169
(WIAPI=> {
170
170
constAPI=newWIAPI('test-integration'); // Note: Replace 'test-integration' with your actual integration identifier.
171
-
API.insert('secondary-content', (elem, meta) => {
172
-
// This element is the a secondary content container on vehicle details pages roughly 2/3 of the way down.
173
-
//It may also be added custom to one or more standalone pages on the website.
171
+
API.insert('primary-banner', (elem, meta) => {
172
+
// This element is typically positioned in a prominent location above the vehicle listings on the Search Results Page.
173
+
//On the Details page, it is near the top of the vehicle information, below the media gallery.
174
174
});
175
175
})(window.DDC.API);
176
176
```
@@ -181,32 +181,41 @@ This element is the media gallery container on vehicle details pages. Injecting
181
181
(WIAPI=> {
182
182
constAPI=newWIAPI('test-integration'); // Note: Replace 'test-integration' with your actual integration identifier.
By default, this element is roughly 2/3 of the way down on vehicle details pages.
203
+
This element is positioned in a prominent location above the vehicle listings on the Search Results Page.
197
204
198
-
Since this may also be present on one or two standalone pages as custom additions, it is likely you will want to target just details pages by first subscribing to the <ahref="#page-load-v1">`page-load-v1`</a> event, then using the <ahref="#page-event">event</a> value of `payload.detailPage` to check the page type.
205
+
On the Details page, it is positioned at the top of the vehicle information, below the media gallery.
199
206
200
-
## Primary Banner
207
+
You can target either the listings or details page by first subscribing to the <ahref="#page-load-v1">`page-load-v1`</a> event, then using the <ahref="#page-event">event</a> values of `payload.searchPage` and `payload.detailPage` to check the page type.
208
+
209
+
## Secondary Content
201
210
202
211
> Usage:
203
212
204
213
```javascript
205
214
(WIAPI=> {
206
215
constAPI=newWIAPI('test-integration'); // Note: Replace 'test-integration' with your actual integration identifier.
207
-
API.insert('primary-banner', (elem, meta) => {
208
-
// This element is typically positioned in a prominent location above the vehicle listings on the Search Results Page.
209
-
//On the Details page, it is near the top of the vehicle information, below the media gallery.
216
+
API.insert('secondary-content', (elem, meta) => {
217
+
// This element is the a secondary content container on vehicle details pages roughly 2/3 of the way down.
218
+
//It may also be added custom to one or more standalone pages on the website.
210
219
});
211
220
})(window.DDC.API);
212
221
```
@@ -217,30 +226,21 @@ Since this may also be present on one or two standalone pages as custom addition
217
226
(WIAPI=> {
218
227
constAPI=newWIAPI('test-integration'); // Note: Replace 'test-integration' with your actual integration identifier.
219
228
API.subscribe('page-load-v1', ev=> {
220
-
if (ev.payload.searchPage||ev.payload.detailPage) {
This element is positioned in a prominent location above the vehicle listings on the Search Results Page.
240
-
241
-
On the Details page, it is positioned at the top of the vehicle information, below the media gallery.
241
+
By default, this element is roughly 2/3 of the way down on vehicle details pages.
242
242
243
-
You can target either the listings or details page by first subscribing to the <ahref="#page-load-v1">`page-load-v1`</a> event, then using the <ahref="#page-event">event</a> values of`payload.searchPage` and`payload.detailPage` to check the page type.
243
+
Since this may also be present on one or two standalone pages as custom additions, it is likely you will want to target just details pages by first subscribing to the <ahref="#page-load-v1">`page-load-v1`</a> event, then using the <ahref="#page-event">event</a> value of `payload.detailPage` to check the page type.
0 commit comments