Escalax Bid Adapter: initial release

[escalax]

Type of change

• Bugfix

• Feature

• New bidder adapter

• Updated bidder adapter

• Code style update (formatting, local variables)

• Refactoring (no functional changes, no api changes)

• Build related changes

• CI related changes

• Does this change affect user-facing APIs or examples documented on http://prebid.org?

• Other

Description of change

Other information

prebid.github.io

[patmmccann]

What is the goal of the dynamic subdomain?

[escalax]

@patmmccann
We have a different subdomain for each region - us, eu and so on

[JulieLorin]

Can you link the PR on prebid docs in this PR description ?

[JulieLorin]

here, you use the subdomain of the first bid for the request.
So if bids uses different subdomain, it would be ignored.
I am guessing you want the publisher to use only one value for subdomain among all bids but this forces the publisher to copy paste the same parameter everywhere.
Another solution could be to set up a parameter in the setConfig/setBidderConfig option so the publisher would only have to set the param once and there would not an issue where only the params from the first bid is used.
You can find a simple example of that with Adot bidder which setup a global publisherId :
https://github.com/prebid/Prebid.js/blob/master/modules/adotBidAdapter.md
https://github.com/prebid/Prebid.js/blob/master/modules/adotBidAdapter.js

[escalax]

@JulieLorin I see, that's reasonable
But wouldn't it be more difficult for the publisher to specify an additional code like in adot example with this publisherId
And what i saw in couple of adapters is region parameter, like here:

Prebid.js/modules/luceadBidAdapter.md

Lines 26 to 40 in 39e6418

	const adUnits=[
	{
	code:'test-div',
	sizes:[[300,250]],
	bids:[
	{
	bidder: 'lucead',
	params:{
	placementId: '1',
	region: 'us', // optional: 'eu', 'us', 'ap'
	}
	}
	]
	}
	];

or here:

Prebid.js/modules/precisoBidAdapter.md

Lines 15 to 19 in 39e6418

	| Name | Scope | Description | Example |
	| :------------ | :------- | :------------------------ | :------------------- |
	| `region` | optional (for prebid.js) | 3 letter country code | "USA" |
	| `publisherId` | required (for prebid-server) | partner ID provided by preciso | PreTest_0001 |
	| `traffic` | optional (for prebid.js) | Configures the mediaType that should be used. Values can be banner, native | "banner" |

We can agree to make a region parameter instead of subdomain and a different endpoint url for each such parameter - US, EU

[patmmccann]

why don't you detect the user region and fill in your own subdomain instead of putting this on the publisher. Here is some basic logic:

function getContinentFromTimeZone(timeZone) {
    // Validate the input timezone
    if (typeof timeZone !== 'string') {
        throw new Error('Invalid timezone: Timezone must be a string.');
    }

    // Map timezone region prefixes to continents
    const continentMap = {
        "Africa": "Africa",
        "America": "North America / South America",
        "Antarctica": "Antarctica",
        "Asia": "Asia",
        "Atlantic": "Atlantic Ocean region",
        "Australia": "Australia",
        "Europe": "Europe",
        "Indian": "Indian Ocean region",
        "Pacific": "Pacific Ocean region",
    };

    // Extract the main region from the timezone string
    const mainRegion = timeZone.split('/')[0];

    // Return the matching continent or a default message
    return continentMap[mainRegion] || "Unknown continent";
}

// Example usage:
const userTimeZone = Intl.DateTimeFormat().resolvedOptions().timeZone;
console.log(`User's timezone: ${userTimeZone}`);
console.log(`Continent: ${getContinentFromTimeZone(userTimeZone)}`);