PageSourceSearch

https://www.officeworks.com.au/resources/tagging/ow-tagging-config.js?v=84.1836

js officeworks.com.au collected 2026-09-24 15:31:38 UTC 1,691 bytes, 37 lines download raw bytes

1//PURE AWESOMENESS
2var owTaggingConfig = {
3    NativeAppGAAccount: "UA-48944962-4",
4    GoogleAnalyticsAccount: "UA-76549432-1",
5    CoremetricsAddToCartTrackingCount:20, //max number of SKU entry in cookie to track add to cart
6    InsideTag: "au11-tracker.inside-graph.com/gtm/IN-1000495/include.js",
7    richRelevanceAccount:'ddce772e3b196319',
8    richRelevanceUrl: '//integration.richrelevance.com/rrserver/',
9    adobeAnalytics: "//assets.adobedtm.com/d6db737b9adb/6f22a0e4d378/launch-46442ca08c28-development.min.js"
10}
11
12//EVEN MORE PURE AWESOMENESS
13/**
14 * Add to this array any paths that should display a banner. The banner will be displayed in any subpaths.
15 *
16 * For example... If the String 'print' were in this array, then for the URL
17 * https://www.officeworks.com.au/print/print-and-copy the /print and all it's sub path pages will display the banner.
18 * @type {string[]}
19 *
20 */
21var approvedWarningPaths = [];
22
23/**
24 * Add to this array any paths that should NOT display a banner. This includes any subpaths as well.
25 * The excludedBannerPath takes precedence over approvedWarning paths.
26 * Take this path for example /print/print-and-copy-signage/28-print-and-copy/102-banners-and-frames
27 *
28 * If the String 'print' were included in the approvedWarningPaths (@see approvedWarningPaths) and the
29 * String '28-print-and-copy' where included in this array. Then the banner will not appear in /28-print-and-copy and
30 * it's subpaths
31 *
32 * Because of this, try to find the highest level you can.
33 * Otherwise you run the risk of excluding banners from places you don't want them excluded from.
34 *
35 * @type {*[]}
36 */
37var excludedBannerPaths = [];

Line numbers count LF bytes from the start of the resource, as the search results do. Vendor segments are library code the classifier recognised; they are stored but not indexed. Bytes are shown as Latin1 characters, one per byte.