Passing multiple wallets

The single biggest lever for many publishers, is passing every wallet you know about for a user.

Most publishers allow users to connect one wallet at a time and have no history of others. But if your platform does know about multiple wallets for a single user, you can pass them as an array to our serve function.

import { specify } from './lib/specify';
import { ImageFormat } from '@specify-sh/publisher-sdk';

// Every address this user controls, not just the connected one
const ad = await specify.serve(
  ['0x1111111111111111111111111111111111111111', '0x2222222222222222222222222222222222222222'],
  { imageFormat: ImageFormat.LANDSCAPE, adUnitId: 'sidebar' }
);

Why this matters so much

• Better targeting, better fill. The more active wallets we have for a user, the clearer the picture of what protocols they use, and the more accurately we can match them to a relevant ad. More matches means more ads served.
• More conversions caught. We track conversion activity across every wallet you pass us. If a user sees your ad and then tests the advertised product on a separate wallet, we still catch the conversion, and you still earn the revenue share.

Only pass wallets the user controls

Many wallet apps let people watch an address they do not own, to follow a whale or monitor a treasury. Filter those out before calling serve(). Pass accounts the user holds keys for, and nothing else.

For other apps, the same applies to any address you display but the user does not control: addresses pasted into a search box etc.

Example: a wallet publisher

A user of your wallet app probably has several accounts set up. You already know all of those addresses.

Pass the full array to serve and:

• We see the complete onchain footprint of the user, not just whichever address they happen to have selected in your UI
• We can attribute conversions across any of their wallets, not just the active one
• Your inventory becomes dramatically more valuable to advertisers, which feeds into your revenue share tier