Опис
Thanks for looking at the Onefeed Integration App. This plugin has 2 main parts. Firstly it creates a Onefeed compatible product feed export for ingesting into the Onefeed platform. The other element of this plugin is to add the Onefeed tracking code to the site. This is a vital part of the service and allows for tracking all paid traffic to your site.
Onefeed is an advertising platform to assist e-commerce advertisers gain better results from Google and Bing advertising. Onefeed’s platform has 2 major benefits.
Firstly we have a feed management and optimisation module that gives users full visibility and control over their product data. This app generates a product feed from your inventory database in a format that is easily digested into the Onefeed platform. This app builds the feed using all your product data and pushes the feed onto a url. The app will automatically update your feed every few hours. The data exported is the essential product information for Google and Bing to use their product advertising services. The data is things like product titles, prices, descriptions etc. No sensitive data is exported in the feed that anyone would consider a breach of GDPR
The second element of this app is to implement the Onefeed tracking code onto the site’s pages and also the checkout process. Onefeed’s goal is to independently track clicks and sales on your site and report the data back through the Onefeed management platform. The tracking tags that this app generates connects through the Onefeed tracking API and gives you intelligent performance reporting of all items purchased in each basket. Details on the data collected is outlined below.
3rd Party Data and Integration Information
Onefeed is a 3rd Party in the WordPress eco-system. We are an advertising management platform that uses data from your WordPress / Woo-commerce website to help you manage your advertising campaigns on platforms like Google and Bing. If you choose to install the Onefeed tracking in the app this will have 2 basic elements. The first element will add tracking code to the site. This will allow Onefeed to report clicks on items in your advertising. The data is collected through the API. The second part of the Onefeed tracking is the order / purchase data. The Onefeed tracking will collect the following purchase information for each conversion:
- Order ID
- Order Amount
- Item(s) Purchased
- New customer flag
- Customer ID
Please note that in the checkout no personal data is processed. We don’t record any payment information nor do we look for or process any personal information.
There are 2 tracking Tags that are implemented in the Onefeed tracking:
Tag 1:
https://tracking.onefeed.co.uk/c.js
The c.js is a cookie-based tracking solution and requires consent from a user before any data is transferred through the API call.
Tag 2:
https://tracking.onefeed.co.uk/hf.min.js
This tag is a cookie-less tracking code that simply records data for a user that is GDPR compliant as no data is stored on the user’s machine. This doesn’t require consent and is the back-up in case the above tracking is blocked or consent is not granted.
Скріншоти



Встановлення
- There are 2 ways to implement this app. The first is through the plugins list. The other way is to upload the zip file through the WordPress plugins directory in your admin.
- Click Activate Plugin.
- Once the app has been installed please go to the ‘Onefeed Toolkit’ Settings. In here please add your SSID. The SSID is your Onefeed tracking ID. This is a number hyphen number format such as ‘145-1’ – please add this in the SSID box. Click Save Settings.
- Click the menu item for ‘Feed Export’ in the Onefeed Toolkit Navigation.
- In here please choose your feed export type – either XML or CSV.
- Select a time for the feed to automatically update – usually early morning is perfect.
- Click Save Settings.
Часті питання
-
How is the tracking implemented?
-
The tracking is automatically implemented when the plugin is added to your store. The landing page scripts and the checkout tracking are installed through the plugin automatically.
-
Can I view my feed?
-
The feed urls are generated on your local FTP location and are in the folder system – wp-content/uploads/onefeed. All Feeds now have a token to load the feed. Without the pre-generated token the feed urls will give an error. This avoids anyone externally calling the feed url and getting all the feed data.
Відгуки
Для цього плагіна немає відгуків.
Учасники та розробники
“Onefeed Tracking and Feed Toolkit” — проект з відкритим вихідним кодом. В розвиток плагіну внесли свій вклад наступні учасники:
УчасникиПерекладіть “Onefeed Tracking and Feed Toolkit” на вашу мову.
Цікавитесь розробкою?
Перегляньте код, перегляньте сховище SVN або підпишіться на журнал розробки за допомогою RSS.
Журнал змін
1.0.9
- Added Product Highlight to the feed, taken from the bullet points in a product’s description. Google’s AI shopping surfaces cannot reliably pull a fact out of prose, so a feature listed as its own highlight can be quoted back in answer to a shopper’s question where the same sentence buried in a paragraph cannot. Lists in the description are read first, falling back to lines beginning with a bullet character for descriptions typed as plain text.
- Added Popularity Rank, worked out from the 90 day sales figures the feed already collects. Products are ranked against the others that actually sold rather than against the whole catalogue: in most catalogues the majority of products sell nothing in any given period, and counting them compresses every real seller into the top few points of the scale. A product with no sales in the period is reported as zero.
- Added Item Group Title, the shared name of a variable product’s family without the variant detail.
- Added Related Products, built from the Upsells and Cross-sells set in a product’s Linked Products panel. Cross-sells are published as accessories and upsells as substitutes. A link pointing at a variable product is expanded to that product’s variations, because the parent of a variable product is not itself a row in the feed and the reference would otherwise lead nowhere. Links to unpublished, grouped or external products are left out for the same reason.
- Added Document Links, listing PDFs linked from the product description. Google accepts PDFs only for this field, so other document types are not collected. Files served from WooCommerce’s protected downloads folder are also left out, because Google cannot fetch them.
- Added Option 1 to 3 Name and Value, carrying whatever a variable product actually varies on. Only Colour and Size were exported before, so a product varying by finish, length, pack size or anything else gave no way to tell its variations apart in the feed.
- Fixed Colour and Size exporting blank on any store that defines them as product level attributes rather than global ones. The feed only ever looked for the global versions, so on a store where the values had been typed straight into the product editor both columns came out empty on every row.
- Fixed HTML entities reaching the feed as literal text. Product names, brands, categories, colours, sizes and shipping classes were exported exactly as stored, so a product named “Rod & Reel” arrived with the entity intact instead of an ampersand. Only descriptions were being decoded before.
- The CSV and XML feeds are now generated from a single definition of the feed’s fields. They were previously built by two separate pieces of code that each listed every field by hand, which is how Colour and Size came to be present in the CSV and absent from the XML altogether, and how the two came to disagree on the created date format. A field added once now appears in both.
- The XML feed gains colour, size, cost_price and product_type elements, all of which the CSV already carried.
- The created date is now written in the same format in both feeds (ISO 8601, for example 2025-01-27T15:08:41). The CSV previously used a plain date with no time.
1.0.8
- Fixed products with very large numbers of variations exhausting memory. Variations were written out and released only after a whole page of products had been processed, so a single product with thousands of variations could hold all of them in memory at once. Each variation is now written and released individually.
- The 90 day sales figures are now calculated with a single database query instead of loading every order from the period into memory, and the result is reused across the stages of an export rather than being rebuilt for each one. On stores with significant order volume this was consuming hundreds of megabytes before the first feed row was written.
- Time and memory budgets are now checked after every product rather than every twenty five, so one unusual product cannot carry a stage past its limits.
1.0.7
- Fixed a false “export failed” message appearing as soon as an export started. The request that sets a job up was being treated as a crash when it handed over to the first stage. The export itself was unaffected and completed normally, but the notice was alarming and wrong.
- A stage that is genuinely cut off part way through is still reported, so real failures are not hidden by the fix.
1.0.6
- The feed export now runs in short stages instead of all in one request. Each stage writes a few hundred rows and hands over to the next, so PHP releases everything in between. Peak memory is now set by the stage size rather than by how many products the store has: a store with 200 products and a store with 200,000 use the same amount. This removes the memory and timeout failures entirely rather than working around them.
- The finished feed only replaces the previous one once the last stage has been written, so a run that is interrupted leaves the existing feed untouched and never publishes a partial file.
- Running an export from the admin screen now shows progress as it goes.
- The scheduled nightly export runs the same way, each stage scheduling the next.
1.0.5
- Fixed the export diagnostics failing in the one case they were most needed. When an export was stopped by the memory limit, the handler that records the reason could not allocate enough memory to write to the database, so nothing was recorded and the merchant saw a blank error page. Progress is now written to a small file on disk as the export runs, and a memory reserve is released before the reason is recorded.
- The Feed Export screen now reports the outcome of the last run, including how far it reached, peak memory against the site’s limit, and the PHP, WooCommerce and plugin versions, in one line that can be passed straight to support.
1.0.4
- The export now reports its own failures on screen. If it stops, the Feed Export page says why, how many products it got through, and what the site’s PHP memory limit is. Previously a failed export produced only WordPress’s generic critical error page, which told the merchant nothing and required server log access to diagnose.
- Added a “Skip shipping cost calculation” setting. Shipping is worked out by running WooCommerce’s own checkout calculation for every product, which is the slowest and most memory hungry part of the export; turning it off lets the rest of the feed export on constrained hosting, leaving the shipping column empty rather than guessing a value.
- The export now stops itself when memory runs low instead of being killed mid-write, so the previous good feed is left intact and a part written file is never published.
- Part written temporary files are removed when a run stops early.
1.0.3
- The catalogue is now read in batches of 100 instead of being loaded in full, and each batch is released afterwards, so memory no longer grows with catalogue size.
- The product statistics are no longer recalculated automatically after an export. Previously an export cleared them and the page it redirected to rebuilt them immediately, scanning the whole catalogue a second time. Figures are now refreshed on request.
- Errors thrown by third party shipping methods on PHP 8 are caught, so one misconfigured carrier plugin no longer aborts the whole export.
- The export no longer fails fatally on hosts where WordPress cannot write to the filesystem directly; it reports the failure instead.
- Long exports are no longer cut short by the host’s execution time limit where that can be raised.
1.0.2
- Added an Additional Images column to the CSV feed, and an additional_images element to the XML feed, listing every gallery image for a product as comma separated URLs. Variations inherit the parent product’s gallery.
1.0.1
- Feed exports are now written to disk row by row instead of being built entirely in memory. Large catalogues no longer exhaust PHP’s memory limit on low-memory hosting. Feed output is unchanged.
- Fixed a fatal error on the order confirmation page when an order contained a line item with a quantity of zero.
1.0.0
- Initial release.