Partner dashboard
Lost your phone? Enter a backup code here — it is six characters too.
Partner accounts are opened by arrangement. Tell us about yourself and how you plan to bring traffic.
Manager’s Telegram@spokynoky32Create an account and get a personal tag — that is what we credit your rewards by.
By creating an account you accept the affiliate program terms and privacy policy.
We sent a code to . Enter it to confirm your email.
The reset code will arrive by email.
If an account is linked to this email, the code will be sent.
Set a new password.
Statistics
Traffic sources
No data yet: sources add up with every click on your link.
Accruals
No sales through your link yet.
Commission rates
Withdrawals
Add payout details first — we need to know where to send the money.
Add payout detailsPayout history
Payout details
No payout details yet — add your first ones.
Links and feed
Your tag is already built into the feed links. Details are on the page API and feeds.
Links for platforms
For a detailed breakdown of traffic by platform.
Google Ads
Google Ads cannot see that a click on your ad ended in a purchase — the purchase happens on our side. The fix: every day we hand Google a file with your customers’ payments, and it credits them to your ads. You set this up once, in three steps.
This is how Google Ads learns what counts as a purchase. In your account open “Goals” → “Summary” → “+ New conversion action” → “Offline conversions”; skip the “data source” step — our file will be the source. In the action settings choose “Every conversion”, value “Use different values for each conversion”, and a 90-day conversion window. Type the action name here character for character: that is how Google finds your conversions in the file. And check that auto-tagging is on (“Admin” → “Account settings”) — without it Google does not tag clicks, and there is nothing to attach the purchase to.
Press “Issue a key” — a file URL, a login and a password will appear. Google will fetch the list of your sales from that URL by itself.
Once the action from step 1 shows up in the lists (that can take a few hours), open “Goals” → “Conversions” → “Uploads”, and the “Schedules” tab on top. Add an HTTPS source, paste the URL, login and password from step 2, and set the frequency to daily. If you have “Data Manager” instead of “Uploads” (“Tools” → “Data Manager”), connect the same file there — it is the same thing.
Purchases do not reach the file immediately, but a day after payment — that is enough time for cancelled orders to drop out. Each purchase is uploaded once and shows up in Google Ads reports within one or two days. If Google skipped a day and did not fetch the file, press , and the purchases that were not uploaded will come back into the file.
The file upload is on, so the browser tag is switched off — otherwise every purchase would be counted twice. To go back to the tag, switch the upload off.
The fallback — a browser tag
You normally do not need it: the file upload is more reliable. But if you want to count conversions with your own tag, create a “Purchase” action in Google Ads with manual code installation and enter the tag ID and the label here. The tag fires on the order delivery page. It only works while the upload above is switched off — together they would count one purchase twice.
Yandex Direct
Connect your Direct account and we will set up the campaigns in it ourselves — PlayStation games and Steam keys: ad groups, ads, keywords and negative keywords, with every link already carrying your affiliate tag. The catalog is updated daily.
The token gives our system access to your Direct account only. It is stored encrypted and is never shown back to you. A Yandex token starts with the letter “y”, a digit from 0 to 3 and an underscore — any token of that shape will do. How to get one is described below.
How to get an OAuth token
1. Open oauth.yandex.ru, press “Create app” and choose the type “For API access or debugging” — the type cannot be changed after the app is created. Fill in “Service name” and “Contact email”, then in the “Data access” field start typing “Direct” and pick from the suggestions “Yandex Direct API access (direct:api)”. Press “Create app”.
2. On the app page copy the ClientID. Sign in to Yandex with the account your Direct runs on, and open the link oauth.yandex.ru/authorize?response_type=token&client_id=YOUR_CLIENT_ID, then press “Allow”.
3. The token will appear in the address bar after access_token= — copy it up to the & sign and paste it in the field above. There is no “show token” button in the Yandex account: it does not keep issued tokens, so save yours straight away. If you lose it, just open the link again.
Connected account:
API and feeds
Your partner link, a product feed for Yandex Direct with your tag, and an open JSON catalog.
1. The affiliate link
Add ?ref=YOUR_CODE to the address of any page on the site. The tag works everywhere: the home page, the catalogs, product pages, top-up pages.
https://jambastore.top/?ref=A7K3M9QPhttps://jambastore.top/playstation/?ref=A7K3M9QPhttps://jambastore.top/playstation/gta-v/?ref=A7K3M9QP
| Rule | How it works |
|---|---|
| Attribution | From the first click, for 30 days. The percentage is credited on every paid order from that customer. |
| The first tag wins | A customer already attributed to another partner moves over to you only once that period runs out. |
| Code format | 8 characters: digits 2–9 and Latin letters, minus the ones that look like digits (0, 1, I and O are not used). |
For social networks and channels there are short links like jambastore.top/g/abc234: the tag and the platform are already inside, and clicks from each platform show up separately in your statistics. Ready-made links are in your dashboard, on the “Links and feed” page.
2. YML product feed with your tag
The whole catalog in YML format. With the ref parameter every offer link already carries your tag — the feed connects to Yandex Direct smart banners and dynamic ads with no extra work.
https://jambastore.top/yml.xml?ref=A7K3M9QP
| What is inside | Details |
|---|---|
| Products | PlayStation games, subscriptions, gift cards, currency and add-ons (DLC), mobile game top-ups, digital services and Steam keys — the active catalog with prices in rubles. PSN and Steam balance top-up pages do not go into the feed. |
| Categories | 8 sections with fixed ids: PS games, subscriptions, cards, currency, DLC, mobile games, services, Steam keys. |
| Collections | On top of categories, products are marked with collections: shop sections, PlayStation selections (games, pre-orders, new releases, sales), genres and service groups. Yandex Direct shows them as feed “collections” — a handy way to build smart banner filters without listing products by hand. |
| Offer fields | url (with your tag), price, picture, name, description, availability. The “Genre” parameter comes with PlayStation products, “Region” with services and Steam keys. |
| Updates | Once an hour. |
| Without a code | /yml.xml serves the same feed without tags. An unknown code gives an untagged feed too — check it in your dashboard. |
3. Feed for Google Merchant Center
The same catalog in the format Google reads: RSS 2.0 with the g: namespace. Merchant Center does not understand YML, so use this address for Google Ads. The ref parameter works the same way — every offer link already carries your tag.
https://jambastore.top/google.xml?ref=A7K3M9QP
| What is inside | Details |
|---|---|
| Offer fields | g:id, g:title, g:description, g:link (with your tag), g:image_link, g:price in rubles, g:availability, g:condition, g:brand, g:google_product_category and g:product_type with our section. |
| No barcodes | The goods are digital and never have a GTIN, so every offer carries g:identifier_exists set to no. Without that mark Google expects a GTIN and demotes such listings, flagging them as incomplete. |
| How to connect it | Merchant Center → “Products” → “Data sources” → add a product data source from a file, give it this address and turn on scheduled fetching. From then on the feed is available both to shopping campaigns and to Google Ads dynamic remarketing. |
| Updates | Once an hour, same as the YML feed. |
| Without a code | /google.xml serves the same feed without tags. |
The purchase happens on our side, so Google Ads cannot see it by itself. The fix is in your dashboard, on the Google Ads page: every day the shop hands Google a file with your customers’ payments, and the conversions are credited to your ads. Auto-tagging has to be on; a purchase reaches the file a day after payment.
4. UTM tags in ads
Rewards are counted by ref and by nothing else. UTM tags are for you, not for us: they let your own statistics show which campaign and which ad brought the customer. Set both at campaign level: in Yandex Direct, in the “URL parameters” field; in Google Ads, in the “Final URL suffix”. The tag then sticks to every link in the ad and survives a change of landing page.
ref=A7K3M9QP&utm_source=yandex&utm_medium=cpc&utm_campaign={campaign_id}&utm_content={ad_id}&utm_term={keyword}
| Parameter | What for |
|---|---|
ref | Your code. The one thing that attributes the customer to you and earns the percentage. Without it the click counts as an ordinary one, even with every UTM tag in place. |
utm_source, utm_medium |
The platform and the traffic type: yandex and cpc for Yandex Direct, telegram and social for a channel. |
utm_campaign, utm_content,
utm_term | The campaign, the ad and the keyword. Yandex Direct fills the values in itself — leave the curly braces as they are. |
| Google Ads | It has placeholders of its own: utm_source=google&utm_medium=cpc&utm_campaign={campaignid}&utm_content={creative}&utm_term={keyword}. They go into the campaign settings: the “Campaign URL options” block → the “Final URL suffix” field, and put ref there as well. The “Tracking template” field is not the place for this. |
| The tag and the feed | If the feed is connected with ?ref=, the tag is already in every link. A duplicate in “URL parameters” breaks nothing: matching values simply repeat. |
| Speed | UTM tags do not slow pages down: caching only takes the meaningful parameters into account and drops the tags. |
5. Links to sections and products
The address structure is stable and safe to hard-code into ads. The full list of landing pages is in the sitemap: https://jambastore.top/sitemap.xml.
| Page | Address | Parameters |
|---|---|---|
| PlayStation catalog | /playstation/ |
type — game, subscription, gift_card,
game_currency, dlc |
| PS selections | /playstation/games/,
/playstation/preorders/, /playstation/new/,
/playstation/sale/, /playstation/subscriptions/,
/playstation/gift-cards/,
/playstation/game-currency/,
/playstation/dlc/ | — |
| PS genres | /playstation/genre/<slug>/ — the slug is in Latin letters, a transliteration of the genre name; the full list is in the sitemap |
— |
| PS product | /playstation/<slug>/ |
edition |
| PSN wallet top-up | /psn-topup/ | — |
| Steam top-up | /steam-topup/ | — |
| Steam games | /steam/,
/steam/<slug>/ | — |
| Mobile games | /donat/,
/donat/<slug>/ | — |
| Services | /services/, /services/g/<category>/, /services/<slug>/ | — |
Add &ref=A7K3M9QP to any address (or ?ref= when there are no other parameters). The region is not added to the address: a PlayStation product page opens on the cheapest region, and the customer switches it right on the page.
6. JSON catalog for storefronts and bots
For your own storefronts, channels and bots. No authorisation or keys needed; responses come as JSON. Call them from your own server or from a bot: the endpoints send no CORS headers, so the browser will block a direct call from a page on another domain.
| Request | What it returns |
|---|---|
GET /api/ps-index/?region=turkey |
The entire active PlayStation catalog as a bare array, with short keys: t — title, s — slug, ty — type, img — image, pr — prices by region, rd — release date, du — end of the sale. Editions come as separate items: ty=edition, with s repeating the slug of the parent game. |
GET /api/ps-search/?q=gta®ion=turkey |
Search across the PS catalog. The answer is an object {items, total, corrected, terms}: items — up to 150 entries in the /api/ps-index/ format, total — the full number of matches. The query is 2 to 80 characters. Typos are corrected only when the original query found nothing. |
GET /api/products/?category=ps®ion=turkey |
Products with prices and images. Categories: ps, steam, mobile, service, steam_keys. Add-ons tied to a game stay out of the ordinary listing — they come back from requests with search, ids, slug or ?dlc=1; ?editions=1 expands games into edition cards. The search filter takes the first 6 words into account, and section only works together with category. |
GET /api/products/?category=steam_keys&offset=500 |
Steam keys come in pages of up to 500 items: total is the full count, next_offset is the offset value for the next page, null on the last one. |
GET /api/steam/ |
The Steam keys catalog: {products, total}, each entry holding id, slug, title, image, from_price (the “from” price), in_stock, is_dlc. With ?count=1 only the number of entries comes back — enough for a caption like “N games” without downloading the catalog. |
GET /api/stats/ |
The number of orders the shop has completed. |
GET /api/reviews/ |
Customer reviews with ratings and shop replies: up to the last 100. With the product_id parameter — reviews with text for one product (gift cards and currency denominations share them across the whole line). |
A product link is built from slug and category: ps — /playstation/<slug>/, mobile — /donat/<slug>/, service — /services/<slug>/, steam_keys — /steam/<slug>/. The tag is added with ?ref=A7K3M9QP. A click from your storefront attributes the customer exactly like an ordinary affiliate link.
7. Analytics goals
The storefront reports the customer’s steps to Yandex Metrica and to Google Analytics 4 by itself. You cannot put your own Metrica or GA counters on our pages — these goals are counted in ours. Google Ads conversions, though, do reach your own account: through the payments file or through your own tag, set up in your dashboard on the Google Ads page. Below you can see which goal fires at which step.
| Customer step | Metrica goal | GA4 event |
|---|---|---|
| Opened a product page | Product view ID 589987886 |
view_item |
| Added to the cart | Add to cart ID 589988600 |
add_to_cart |
| Went to checkout | Checkout started ID 589977373 |
begin_checkout |
| Paid for the order | Paid order ID 589977698 |
purchase |
The “Paid order” goal carries the amount (order_price, currency RUB) and the order id (order_id) — that is what campaign revenue is counted from. GA4 receives the same amount and the order contents: value, currency and transaction_id.
Limits and rules
| The feed is rebuilt once an hour: asking more often returns the same file. |
Two responses are cached: /api/ps-index/ — 5 minutes on the server and 10 minutes in the browser, and /api/products/ with the category parameter (without search, ids or slug) — 5 minutes. The rest are recomputed on every request. |
Request rates are limited: /api/ps-search/, /yml.xml and /google.xml — 120 requests an hour per address, /api/products/ — 600 an hour. Over the limit you get a 429 — repeat the request later. Poll the other endpoints no more than once a minute. |
| Ads that speak in the name of Jamba Store, and bidding on our name as a keyword, are forbidden by the program rules. |
Support chat
Our contacts
A Telegram contact to reach you
Security
Recent sign-ins
No sign-in records yet.
Two-factor authentication
Open your authenticator app and add the key in one of two ways.
The QR code is unavailable right now — add the key by hand.
Code from the app
Enter six digits.
Are you sure you want to turn 2FA off?
The account will be protected by the password alone. Enter six characters — a code from the app or a backup one.
The old codes will stop working. Enter your password to get a new set.
Backup codes. Keep them: they let you sign in when your phone is not at hand. Each one works once.
Change password
Password reset
The reset code will arrive by email.
The code from the email
If an account is linked to this email, the code will be sent.
New password
Close your partner account?
This cannot be undone. Here is what happens:
- Sign-in will be closed for good and cannot be restored.
- Accruals will stop: the customers tied to you will no longer earn you a percentage.
- Payout details, support conversations and links will be erased.
- Your partner code will stop working — links in your posts will lead to the shop without a tag.
The data we need for accounting — the amounts and dates of payouts already made — stays with us, anonymised.