Vector

Vector identifies the people and companies visiting your site and builds advertising audiences from their activity. The c15t vector helper keeps Vector off the page until the marketing category is allowed. Vector has no documented stop API, so on withdrawal c15t reloads the page to stop it.

Configure Vector

Copy the pixel ID from Settings > Pixel in your Vector account, where the install snippet calls vector.load. Vector's own consent example requires advertising consent, so this helper uses the marketing category. Remove the direct snippet and any tag manager copy so they can't bypass c15t.

npm install @c15t/integrations

pnpm add @c15t/integrations

yarn add @c15t/integrations

bun add @c15t/integrations

import { vector } from '@c15t/integrations/vector';

export const scripts = [vector({ pixelId: 'YOUR_PIXEL_ID' })];

Register the scripts

Complete your framework quickstart first. Keep its Inth endpoint, policy, styles and consent UI. Remove the vendor's original script, SDK initializer or tag-manager entry, so the vendor loads only through c15t.

The vendor pages put the helper in src/consent-scripts.ts. If your framework quickstart already has a scripts array, such as the one in c15t.config.ts in the Next.js guide, add the helper to that array instead of creating a second file. The scripts export is a configuration, not an initializer. Add it to the c15t provider you already have, at the registration point for your framework below. These are edits to that provider, not a second provider.

import { defineConsentConfig } from 'c15t/next';
import { scripts } from './src/consent-scripts';

export default defineConsentConfig({ scripts });

Options

Loading and revocation

After consent, the helper creates window.vector with a queue for load, identify and on. Calls use Vector's nested argument format, [methodName, argsArray], and preserve callback references. The helper queues load(pixelId) before inserting the asynchronous SDK script. Existing SDK methods are preserved. The helper sends no identification calls itself.

The loader stays registered across withdrawal and regrant to avoid duplicate execution on the same page. Vector has no documented complete shutdown API. Keep c15t's default page reload on revocation enabled. With reload disabled, running code, pending loads and partner activity can continue until navigation. The reload doesn't clear Vector's storage.

The helper does not call the undocumented block or removeVisitor methods. Form listening and IP-to-company lookup depend on account settings. Vector's IP-to-company consent hooks cover only that lookup and cannot replace gating the whole pixel.

Requests, cookies and storage

Vector's CSP guide lists cdn.vector.co, api.vector.co and a.usbrowserspeed.com. The current SDK also includes LiveIntent and can contact idx.liadm.com. Check requests for your account before setting CSP rules.

The current SDK prefers local storage, with session storage, cookies and memory as fallbacks. Pixel state can include vector_pixel_<pixelId>_visitor_id, vector_pixel_<pixelId>_visitor_uuid, vector_pixel_<pixelId>_synced_at and vector_pixel_<pixelId>_last_identified_id. Legacy and global keys also exist.

The vector_visitor_id cookie depends on the account's pixelCookieFallback setting. The fetched SDK requests a lifetime of 3,650 days, with SameSite=None; Secure; browsers may shorten that lifetime. Partner state can include _lc2_fpi, _lc2_fpi_js, _li_dcdm_c and local-storage _li_duid. Vector can read the existing hubspotutk cookie. This list describes the fetched SDK, not a stable or exhaustive storage contract.

Verify Vector

Use your own pixel ID on a domain allowed by your Vector account. In a fresh browser profile, deny optional consent, then grant only measurement consent. Confirm that no Vector global, SDK request or vendor storage appears. Grant marketing consent and confirm that pixel.js loads once. Withdraw consent and confirm the page reloads and blocks Vector on the new page. Check Network, cookies, local storage and session storage.

c15t's live vendor probe uses a placeholder pixel ID. It confirms that the downloaded SDK replaces the queue, replays the nested calls and registers the pixel. It blocks settings, identity and collection requests, so the SDK can log a JSON error for the empty settings response. Vector checks the requesting domain before it returns settings, so the probe can't verify account settings or visitor identification. Test those with your own pixel ID on an allowed domain.

Sources: installing the Vector pixel, Vector's Termly consent example, CSP settings, Vector's privacy policy, and the current pixel SDK.

Test in a private window with an opt-in policy. Open DevTools Network, disable the cache and filter by the vendor's domain:

1. Load the page. No request goes to the vendor before you choose.
2. Click Reject, then reload. There is still no vendor request.
3. Open Privacy settings and allow the helper's category. The vendor script loads without a page reload.
4. Turn the category off again and save. c15t reloads the page, and the new page makes no vendor request.

c15t reloads on revocation because removing a script element does not stop code that already ran. The vendor's listeners, timers and queued events stay alive until the page unloads. If you set reloadOnConsentRevoked: false, stop the vendor yourself. Register a callback-only script whose onConsentChange calls the vendor's opt-out API, as shown in custom integrations, and check the permission before each of your own event calls. The reload does not delete cookies the vendor already set; see clear on revocation for your framework.

The helper lists its vendor by name in the preference dialog, so a visitor can turn it off inside an allowed category. See vendor consent for your framework. The consent verification guide covers navigation, expiry and hosting checks.