<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Foxy.io Blog</title>
	<atom:link href="https://www.foxy.io/blog/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.foxy.io/blog</link>
	<description>Ecommerce tips, best practices, and more from the Foxy team.</description>
	<lastBuildDate>Wed, 16 Oct 2024 23:05:02 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.4.2</generator>

<image>
	<url>https://www.foxy.io/blog/wp-content/uploads/2017/11/favicon-60x60.png</url>
	<title>Foxy.io Blog</title>
	<link>https://www.foxy.io/blog</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>The New Foxy Admin is Live!</title>
		<link>https://www.foxy.io/blog/the-new-foxy-admin-is-live/</link>
					<comments>https://www.foxy.io/blog/the-new-foxy-admin-is-live/#respond</comments>
		
		<dc:creator><![CDATA[Brett Florio]]></dc:creator>
		<pubDate>Wed, 16 Oct 2024 23:00:21 +0000</pubDate>
				<category><![CDATA[Product Updates]]></category>
		<guid isPermaLink="false">https://www.foxy.io/blog/?p=5087</guid>

					<description><![CDATA[We are extremely pleased to announce the launch of the new Foxy Admin, available at admin.foxy.io. This brings a few changes: New user signup is now exclusively available through the new admin. New store creation will be restricted to the new admin very soon. User-to-store management is exclusively available through the new admin. We&#8217;ve moved [&#8230;]]]></description>
										<content:encoded><![CDATA[<p>We are <em>extremely</em> pleased to announce the launch of the new Foxy Admin, available at <a href="https://admin.foxy.io/">admin.foxy.io</a>. This brings a few changes:</p>
<ul>
<li>New user signup is now exclusively available through the new admin.</li>
<li>New store creation will be restricted to the new admin very soon.</li>
<li>User-to-store management is exclusively available through the new admin. We&#8217;ve moved to a new invitation approach that isn&#8217;t supported in the legacy admin.</li>
</ul>
<p>The new admin has a variety of new features previously unavailable in the legacy admin, including but not limited to:</p>
<ul>
<li>Gift cards</li>
<li>User-attributes and user-subscription restrictions and auto-apply functionality for coupons</li>
<li>New reporting. (We&#8217;ll be adding a legacy formatted CSV/TSV export to the new admin in the future.)</li>
<li>Customer portal settings</li>
<li>Customer management</li>
</ul>
<p>Please contact us if you have any feedback, feature requests, or bug reports. Thanks so much for trusting Foxy with your ecommerce needs.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://www.foxy.io/blog/the-new-foxy-admin-is-live/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Tax-inclusive Pricing Is Here</title>
		<link>https://www.foxy.io/blog/tax-inclusive-pricing-is-here/</link>
					<comments>https://www.foxy.io/blog/tax-inclusive-pricing-is-here/#respond</comments>
		
		<dc:creator><![CDATA[Josh Bartolomucci]]></dc:creator>
		<pubDate>Tue, 21 May 2024 19:45:23 +0000</pubDate>
				<category><![CDATA[Product Updates]]></category>
		<guid isPermaLink="false">https://www.foxy.io/blog/?p=5068</guid>

					<description><![CDATA[We're excited to announce that tax-inclusive pricing is now available for all Foxy users.]]></description>
										<content:encoded><![CDATA[<p>We&#8217;re excited to announce that tax-inclusive pricing is now available for all Foxy users. For those unfamiliar, tax-inclusive pricing displays the product price with tax included, but also displays taxes charged as a separate line item.</p>
<p>For example, assume an $83.33 product and a 20% tax. In both cases, the item should be <code>price=83.33</code>. (Note that there may be situations where, due to rounding, you may need to specify a more accurate price, such as <code>price=83.3333</code>. Foxy can handle that specificity to fix rounding issues.)</p>
<ul>
<li>In a tax-exclusive cart, the item will be displayed as $83.33, the tax will be $16.67, and the order total will be $100.</li>
<li>In a tax-inclusive cart, the item will be displayed as $100, the tax will be $16.67 (and will show an “inclusive” note in the heading), and the order total will still be $100.</li>
</ul>
<p>In that sense, this update can be considered a “display only” change. All other aspects of Foxy&#8217;s tax functionality remain effectively unchanged. For example, a tax-exempt customer will pay the price value of the item(s) in the cart, and it will look identical to how it&#8217;d look for a tax-exclusive cart. Also, you can still have taxed and non-taxed products in the same order (ie: tax products from your shop but don&#8217;t tax donations).</p>
<p>If you would like tax-inclusive pricing enabled for your store, please <a href="https://foxy.io/contact">contact us</a> to let us know. Alternatively, you can enable tax-inclusive pricing via the Foxy API.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://www.foxy.io/blog/tax-inclusive-pricing-is-here/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Foxy + WigWag</title>
		<link>https://www.foxy.io/blog/foxy-wigwag/</link>
					<comments>https://www.foxy.io/blog/foxy-wigwag/#respond</comments>
		
		<dc:creator><![CDATA[Josh Bartolomucci]]></dc:creator>
		<pubDate>Wed, 08 May 2024 14:38:11 +0000</pubDate>
				<category><![CDATA[Product Updates]]></category>
		<guid isPermaLink="false">https://www.foxy.io/blog/?p=5056</guid>

					<description><![CDATA[South African merchants can now easily accept payments with Foxy + WigWag.]]></description>
										<content:encoded><![CDATA[<p>We&#8217;re excited to announce our latest gateway integration, <a href="https://www.wigwag.me/" rel="noopener" target="_blank">WigWag</a> (powered by Stitch).</p>
<p>WigWag is a payments company dedicated to serving online businesses in South Africa by enabling them to accept card payments from both local and international banks.</p>
<p>With Foxy + WigWag, South African merchants can now sell just about any type of product (physical, digital, subscriptions, services, donations, etc.) on any website or platform (Webflow, Squarespace, Wix, Weebly, WordPress, and more).</p>
<p>In addition to WigWag&#8217;s world-class support, their digital onboarding is one of the fastest in the industry. Only takes 15 minutes to apply for an account and most merchants can start selling same day. Apply for your account <a href="https://just.wigwag.me/signup" rel="noopener" target="_blank">here</a>.</p>
<p>Once your WigWag account is ready, you can easily connect your Foxy store to it by following <a href="https://wiki.foxycart.com/gateways/wigwag" rel="noopener" target="_blank">these instructions</a>.</p>
<p>As always, we&#8217;re here to help if you have any questions or run into any issues. Please don&#8217;t hesitate to <a href="https://foxy.io/contact" rel="noopener" target="_blank">contact us</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://www.foxy.io/blog/foxy-wigwag/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>FoxyShop (WordPress Plugin) Updates</title>
		<link>https://www.foxy.io/blog/foxyshop-wordpress-plugin-updates/</link>
					<comments>https://www.foxy.io/blog/foxyshop-wordpress-plugin-updates/#respond</comments>
		
		<dc:creator><![CDATA[Josh Bartolomucci]]></dc:creator>
		<pubDate>Fri, 29 Mar 2024 15:38:53 +0000</pubDate>
				<category><![CDATA[Product Updates]]></category>
		<guid isPermaLink="false">https://www.foxy.io/blog/?p=5048</guid>

					<description><![CDATA[We see you WordPress users. We've got a new plugin version with multiple updates and bug fixes.]]></description>
										<content:encoded><![CDATA[<p>Dear FoxyShop users,<br />
We haven&#8217;t forgotten about you. FoxyShop (our WordPress PLugin) is still alive, being maintained, and has many Foxy users managing their store/products with it.</p>
<p>We&#8217;re excited to announce that FoxyShop is now on version 4.9.4. We&#8217;ve modernized the codebase to the latest WordPress standards, introduced support for a custom api key, allowed for displaying orders hidden in the Foxy app, made some a11y (accessibility) improvements, added a Brasilian Portugeuse translation, and other updates and bug fixes.</p>
<p>Full details about our free WordPress plugin can be found <a href="https://wordpress.com/plugins/foxyshop" rel="noopener" target="_blank">here</a>. As always, we&#8217;re here to help if you have any questions. Please don&#8217;t hesitate to <a href="https://foxy.io/contact" rel="noopener" target="_blank">contact us</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://www.foxy.io/blog/foxyshop-wordpress-plugin-updates/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Fraudsters are getting so advanced it doesn&#8217;t make sense</title>
		<link>https://www.foxy.io/blog/fraudsters-are-getting-so-advanced-it-doesnt-make-sense/</link>
					<comments>https://www.foxy.io/blog/fraudsters-are-getting-so-advanced-it-doesnt-make-sense/#respond</comments>
		
		<dc:creator><![CDATA[Brett Florio]]></dc:creator>
		<pubDate>Wed, 20 Dec 2023 22:30:09 +0000</pubDate>
				<category><![CDATA[Best Practices]]></category>
		<category><![CDATA[Security]]></category>
		<guid isPermaLink="false">https://www.foxy.io/blog/?p=5014</guid>

					<description><![CDATA[I hate fraud. So much. Twice in the past year we’ve seen fraud so advanced it didn’t make sense. I want to share these experiences because I find them fascinating, and in the hope it prevents more victims. I also hope that this discussion normalizes discussing fraud. It’s a massive industry causing both long-lasting financial [&#8230;]]]></description>
										<content:encoded><![CDATA[<p>I hate fraud. <a href="https://www.youtube.com/watch?v=x9LI9PaL_qQ" target="youtube" rel="noopener">So much.</a></p>
<p>Twice in the past year we’ve seen fraud so advanced it didn’t make sense. I want to share these experiences because I find them fascinating, and in the hope it prevents more victims.</p>
<p>I also hope that this discussion normalizes discussing fraud. It’s a <em>massive</em> industry causing both long-lasting financial and emotional pain to its victims, but we as a society won’t be able to effectively educate and prevent it if the true scope and impact aren’t better appreciated.</p>
<h2>&#8220;Too good to be true,&#8221; but it&#8217;s true?</h2>
<p>Last holiday season, while visiting my parents for the holidays, I experienced a very weird attempted fraud. While 3 generations enjoyed the time, my dad was on an extended phone call that just would not end.</p>
<p>We could tell it was something about their DirecTV service, and eventually started asking, “Dad’s getting scammed, isn’t he?”</p>
<p>We made sure he wasn&#8217;t giving any payment or banking info, and waited for the call to end. Thirty minutes later…</p>
<p>&#8220;So that was a scam call, right?&#8221;</p>
<p>&#8220;No! It&#8217;s actually a really good deal.&#8221; He explained how Google and DirecTV are doing a promo, and he got a free month of service <em>and</em> a free pay-channel <em>just for taking the call</em>.</p>
<p>That’s what the fraudster <em>led</em> with.</p>
<p>The actual “deal” was a reduced monthly rate (sounded reasonable). He just needs to go to Home Depot to get some gift cards, then call the special number to read them the codes, and they&#8217;d do the free promo thing!</p>
<p>Now, my dad’s not stupid, but he didn’t know gift cards = scam. There’s lots of stuff to know, and nobody can know it all. But still, something must have felt phishy, right? <em>Right?!</em>
</p>
<p>No, because…</p>
<h3>They paid his bill?</h3>
<p>&#8220;No, look! They already gave us a free month and turned on a pay channel!&#8221;</p>
<p>He shows us the TV with the newly unlocked pay channel, and the email from DirecTV showing a ~$150 credit to the account.</p>
<p>The email was legit: the SPF, DKIM, and DMARC showed it came from DirecTV, and that a payment had indeed been made to their account. Their online account also showed the payment.</p>
<p>Oddly, the last 4 digits of the card used didn’t match any of my parents’ cards. The fraudster, while on the phone with my dad, paid my parents’ bill using a stolen credit card.</p>
<p>That’s… weird.</p>
<h3>Time to call DirecTV.</h3>
<p>We called DirecTV about this obviously-a-scam situation, and the conversation ended something like this:</p>
<p>&#8220;Yeah, <em>you</em> just made that payment to the account. You don&#8217;t owe any money! You’re all good! Also, my system won&#8217;t give me any information on why/who/how the free premium channel is on the account.”</p>
<p>Not helpful. Oh well. We tried.</p>
<h3>The rabbit hole goes deeper.</h3>
<p>While we saved my dad from becoming a victim and feeling that particular shame, I still had no idea what happened.</p>
<p>We pieced together a few things:</p>
<ul>
<li>The fraudster knew my dad’s DirecTV account info. Knew that he was a DirecTV customer. We don’t know for certain if my dad provided the account number at the beginning of the call, but he doesn’t think he did. But it was a targeted call, regardless.</li>
<li>The fraudster wasn’t working alone. We’re not sure exactly how it happened, but fraudster #2 was likely on the phone with DirecTV modifying the account, perhaps just relaying back my dad’s security answers to the DirecTV, or perhaps something more problematic.</li>
<li>The fraudster has stolen credit cards they use to pay bills, to gain trust with victims.</li>
<li>This was a finely-tuned machine. They had the opening salvo ready to go, with a great incentives just to listen to the “offer”. For those who haven’t seen <a target="_blank" href="https://www.youtube.com/watch?v=VrKW58MS12g&amp;pp=ygUQTWFyayBSb2JlciBmcmF1ZA%3D%3D" rel="noopener">Mark</a> <a target="_blank" href="https://www.youtube.com/watch?v=xsLJZyih3Ac&amp;pp=ygUQTWFyayBSb2JlciBmcmF1ZA%3D%3D" rel="noopener">Rober</a> or <a target="_blank" href="https://www.youtube.com/@JimBrowning" rel="noopener">Jim Browning’s </a> work on YouTube, a lot of these operations have dozens or hundreds of employees. It’s big business.</li>
</ul>
<p>In digging into this, I found <a target="_blank" href="https://forums.directv.com/conversations/directv-account/directv-hacked-and-information-stolen/610bf026ec3d744e306b97ea" rel="noopener">other victims discussing this on the DirecTV forums</a> going back years. I cannot speak to others’ experiences, but it seems likely that DirecTV customer data is/was leaked, allowing direct targeting.</p>
<p>At the time, I had a family party to get back to, but I continued thinking about it for months afterwards, until…</p>
<h2>Airline fraud, kinda-sorta?</h2>
<p>A friend and partner of ours, David at <a target="_blank" href="https://www.merchant-accounts.ca/" rel="noopener">Merchant-Accounts.ca</a> (highly recommended if you want a more personal but still highly competitive payment processing service), emailed asking for our thoughts on some weird fraud he was seeing related to an airline. Here’s what happens:</p>
<ol>
<li>Someone searches for a flight and finds a site selling tickets for a good price.</li>
<li>The customer pays for the ticket(s), enters all their info, and receives their ticket(s). All good so far.</li>
<li>The customer shows up at the airport, gets on the flight and flies with no issue… or they’re told the tickets were fraudulently purchased, charged back, and/or canceled due to fraud.</li>
<li>Either way, whether they flew or not, the customer thinks they have legitimately purchased airfare. They have no idea that they were involved in a scam. Some of them even got to fly as expected. How could it be fraud?</li>
</ol>
<p>Makes no sense, right? How is a fraudster coming out ahead here?</p>
<p>Eventually, one of the airline’s employees showed up at the gate for a flight with a different airline and the same thing happened to them. Tickets were canceled because they were fraudulently paid for.</p>
<p>For a period of time it was quite confusing, but eventually the scam started to become more clear.</p>
<h3>How the fraud works (we think):</h3>
<p>The entry to the fraud is in step #1 above. When the victims are searching for flights, they somehow end up on the fraudster’s website. It looks legit enough to fool people. Maybe it’s a typo-squatted domain. Maybe it’s just a nicely done up site that looks reasonable, and scrapes Expedia/Orbitz/whatever.</p>
<p>To make the fraud more effective, the fraudster takes 10% off the <em>actual</em> cost of the ticket. The victim completes the purchase by entering their credit card info. Behind the scenes a real ticket is bought for this customer, <em>paid for by the fraudster using a stolen credit card</em>.</p>
<p>Even if the customer had concerns about the legitimacy of the website, they end up getting a real ticket at a good price, so no need to bother looking twice.</p>
<p>If the purchaser travels soon enough, it’s unlikely that the owner of the stolen credit card will realize the fraud. In this case the passenger would fly, get what they expected and be none the wiser. But sometimes the airline ends up getting a chargeback and canceling the tickets before the travel date, which is how the airline started to become aware of the scam.</p>
<h3>Where is the benefit to the fraudster?</h3>
<p>Fraudsters aren’t usually so kind as to legitimately provide real things to the people they are defrauding. However, the fraudster still had something of value: the victims money. So let’s think about the transaction flow.</p>
<p>Our suspicion is that the fraudsters have set up a new merchant account to use in their fraud. It’s not getting chargebacks (for the most part) because people are getting actual tickets. Even though the fraudster is selling the ticket at a discount, they have managed to bring their cost to zero, since they’re buying their inventory with stolen credit cards. The fraudster’s unlikely to get chargebacks, at least for a while, because the victim got the service and is blissfully unaware.</p>
<p>It’s only if the <em>first</em> victim (whose stolen card was used to buy the <em>second</em> victim’s – the travelers – tickets) notices the purchase and catches it in time that the tickets are canceled, and the fraud becomes apparent. At that time though, the fraudsters have made off with the funds. David had this to say, which is at least one possibility:</p>
<p>&gt; The merchant account is probably opened fraudulently, but run in good standing, at least for a period of time. The payment processor is funding out all the money that’s been processed to what they think is a legitimate and well run travel agency. The worst fraudsters are the organized, patient ones. We once had a merchant run their merchant account clean for a year. Then said they were going to do a huge weekend so we bumped up their allowed trading volumes. They did a huge pile of volume, we funded them out (after “knowing” them for a year) – and then boom, they’re gone and chargebacks pour in.</p>
<p>This airline fraud got me thinking about the DirecTV fraud I’d experienced firsthand. In both cases, the question remained:</p>
<h2>But still: Why bother stealing money from card #2 if they already have stolen card #1?</h2>
<p>The fraudster clearly already has a stolen card that <em>works</em>. They can buy airline tickets or pay a DirecTV bill. Why not just use that to buy what they want in the first place</p>
<p>What we currently believe (but is just our opinion) is that the answer is money laundering:</p>
<h3>Gift cards are like cryptocurrency: easy to lose, and fantastic for criminals.</h3>
<p>Credit cards can be charged back. Bank transfers can be traced. Wire transfers are a pain in the ass. Crypto’s an even bigger pain in the ass (especially for new users; also, crypto feels more scammy).</p>
<p>But gift cards? Easily and immediately accessible at just about any grocery or big box store. A fraudster can even spin a story about how Google and DirecTV are partnering, so get Google gift cards!</p>
<p>The fraudster already <em>has</em> stolen credit cards, but they can’t really <em>use</em> a stolen card for a lot of things. Can’t use it to pay rent. Can’t use it to pay for anything that’ll trace back to you (or your criminal organization).</p>
<p>What the fraudster <em>wants</em> is untraceable, easy money.</p>
<p>Gift cards, unlike the credit cards, can be used effectively anonymously, and they can be sold (for a little under value) on ebay. (I’d like to believe the degree to which ebay knowingly profits off this is limited, but I’d be <em>very</em> keen to see any additional research on this topic.)</p>
<p>By using a stolen card to gain trust and buy time with the victim (either by actually purchasing airline tickets or by paying a DirecTV bill), they can launder a stolen card into gift cards.</p>
<h2>Takeaways?</h2>
<h3>Data leaks facilitate fraud.</h3>
<p>Does it matter that fraudsters know you have an account at DirecTV? You might not think so, but in this case it was used to more effectively target victims.</p>
<p>Unfortunately, data leaks will continue. If you haven’t already, try putting your email into <a target="_blank" href="https://haveibeenpwned.com/" rel="noopener">haveibeenpwned.com</a>. If your email returns nothing, congrats. I’m in there 7 times for my personal and 10 times for my work emails, and that’s almost certainly not the extent of it.</p>
<p>Take a defensive posture when it comes to what information you assume a fraudster might know about you. Speaking of which…</p>
<h3>Never provide personal info on an inbound call.</h3>
<p>Did your bank call you? No they didn’t. Even if they did, they didn’t.</p>
<p>Ask for a callback number that you can verify on their public website, then call them back. No reputable company should have a problem with it. And if they do, they’re wrong.</p>
<p>This’ll nip most things in the bud. Little extra hassle, and you might need to wait on hold when you call in, but it’s better than risking it. (Caller ID is easily faked.)</p>
<h3>Don’t judge fraud victims.</h3>
<p>Everybody’s been taken for a ride in one way or another. Everybody’s clueless about something “obvious” to somebody else. With data leaks (and AI being able to impersonate voices), highly targeted fraud is becoming more commonplace.</p>
<h3>Tell your family.</h3>
<p>The AARP has a good explanation of <a target="_blank" href="https://www.aarp.org/money/scams-fraud/info-2020/ebay-gift-card-scam-wish-lists.html" rel="noopener">what to never do with gift cards</a>. Let your family know: “<strong>gift cards are for gifts, NOT for payments</strong>.”</p>
<h2>We should talk more about fraud.</h2>
<p>I don’t think we, as a society, talk about fraud and betrayal enough. Yes, we hear about big frauds on the news. <a target="_blank" href="https://www.youtube.com/watch?v=Hzko-cjHhTg" rel="noopener">Coffeezilla’s exploration of the Sam Bankman-Fried / FTX fraud</a> is incredible, and I highly recommend watching it.</p>
<p>But that’s HUGE fraud. What about small fraud? Not $15B but $1.5k? There’s a lot of shame associated with being the victim of a fraud, but I’d wager <em>most</em> people have been defrauded at least once by the time they hit their 40s. Or taken advantage of by an abusive or manipulative person. Different, but (I think) similar in the shame it can leave behind.</p>
<p>Businesses, also, are loath to talk about being victimized. I get it. There are myriad reasons to keep quiet and few incentives to be open. But it’s the thieves who benefit from our culture of silence. Nobody wants to admit to being taken advantage of, but humans often are pretty helpless as individuals. It’s only by sharing our knowledge and experiences that we can make the meaningful, lasting changes necessary to reduce fraud.</p>
<p>–</p>
<p>We work hard at Foxy to maintain the most secure environment and company culture we can. We are a Level 1 Service Provider (the highest level) with PCI, on Visa’s and MasterCard’s global registries, and we’re externally audited annually to ensure we’re doing the best we can.</p>
<p>We don’t take the trust our users place in us lightly. Please reach out if you have any questions about our security, or anything else we can help you with.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://www.foxy.io/blog/fraudsters-are-getting-so-advanced-it-doesnt-make-sense/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Native Support Added For Google Analytics 4 (GA4) and Google Ads</title>
		<link>https://www.foxy.io/blog/native-support-added-for-google-analytics-4-and-google-ads/</link>
					<comments>https://www.foxy.io/blog/native-support-added-for-google-analytics-4-and-google-ads/#respond</comments>
		
		<dc:creator><![CDATA[Josh Bartolomucci]]></dc:creator>
		<pubDate>Fri, 09 Jun 2023 17:34:41 +0000</pubDate>
				<category><![CDATA[Product Updates]]></category>
		<guid isPermaLink="false">https://www.foxy.io/blog/?p=4994</guid>

					<description><![CDATA[Universal Analytics is going away, but GA4 support is here.]]></description>
										<content:encoded><![CDATA[<p>If you have been using Google Analytics with your Foxy store (likely along with our native integration), then you will most certainly be aware that Google Analytics are in the process of deprecating their legacy Universal Analytics product in favor of the newer GA4. Universal Analytics will officially stop processing data on the 1st of July 2023, at which time you will need to be using GA4 to continue collecting analytics.</p>
<p>Our existing GA integration utilises Universal Analytics, and while we’ve had a standalone snippet which could be added to your store to support tracking with GA4 for a little while now, we now have native support for the newer integration through Google Tag.</p>
<p>If you’ve used Google’s GA4 Setup Assistant to configure a new GA4 property linked to your existing Universal Analytics tags, then you may be able to continue to use our existing integration moving forward without making any changes. With that said though &#8211; for future-proofing your analytics, and also making use of the better ecommerce tracking that our GA4 integration includes, we would recommend making the switch to our new integration.</p>
<p>Along with the new integration adding support for the newer GA4, it also now supports Google Ads for tracking conversions (either with just Ads, or with GA4 at the same time). It also adds native support for stores using Google Tag Manager to manage their website tags instead of adding the gtag.js directly.</p>
<p>You can see information about configuring the new Google Tag integration with either your GA4, GTM or Google Ads account <a href="https://wiki.foxycart.com/v/2.0/analytics" rel="noopener" target="_blank">here</a>. As always, we&#8217;re here to help if you need anything at all. Please don&#8217;t hesitate to <a href="https://foxy.io/contact">contact us</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://www.foxy.io/blog/native-support-added-for-google-analytics-4-and-google-ads/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Changes for 2023-05-26</title>
		<link>https://www.foxy.io/blog/changes-for-2023-05-26/</link>
					<comments>https://www.foxy.io/blog/changes-for-2023-05-26/#respond</comments>
		
		<dc:creator><![CDATA[Sami Fiaz]]></dc:creator>
		<pubDate>Fri, 26 May 2023 18:30:04 +0000</pubDate>
				<category><![CDATA[Changelogs]]></category>
		<guid isPermaLink="false">https://www.foxy.io/blog/?p=4972</guid>

					<description><![CDATA[Changes for 2023-05-26 • fix(apple-pay): better logs for decrypting response • feat(cardstream): add support for `orderref` • fix(bank-of-america): add reason node, only for MasterCard • fix(authorize-net-cim): use `1` as amount for verify transactions]]></description>
										<content:encoded><![CDATA[<p>Changes for 2023-05-26<br />
• fix(apple-pay): better logs for decrypting response<br />
• feat(cardstream): add support for `orderref`<br />
• fix(bank-of-america): add reason node, only for MasterCard<br />
• fix(authorize-net-cim): use `1` as amount for verify transactions</p>
]]></content:encoded>
					
					<wfw:commentRss>https://www.foxy.io/blog/changes-for-2023-05-26/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Changes for 2023-05-10</title>
		<link>https://www.foxy.io/blog/changes-for-2023-05-10/</link>
					<comments>https://www.foxy.io/blog/changes-for-2023-05-10/#respond</comments>
		
		<dc:creator><![CDATA[Sami Fiaz]]></dc:creator>
		<pubDate>Wed, 10 May 2023 18:35:26 +0000</pubDate>
				<category><![CDATA[Changelogs]]></category>
		<guid isPermaLink="false">https://www.foxy.io/blog/?p=4984</guid>

					<description><![CDATA[Changes for 2023-05-10 • fix(bambora): ensure exp updates go to Bambora • fix(lang): Dutch translation optional string needs proper formatting • docs(admin): Replace references to the forum • fix(auth.net-cim): add error for null customer profiles • fix(auth-net-cim): update validation mode to use live mode for verification • fix: remove some logging related to JWT generation]]></description>
										<content:encoded><![CDATA[<p>Changes for 2023-05-10<br />
• fix(bambora): ensure exp updates go to Bambora<br />
• fix(lang): Dutch translation optional string needs proper formatting<br />
• docs(admin): Replace references to the forum<br />
• fix(auth.net-cim): add error for null customer profiles<br />
• fix(auth-net-cim): update validation mode to use live mode for verification<br />
• fix: remove some logging related to JWT generation</p>
]]></content:encoded>
					
					<wfw:commentRss>https://www.foxy.io/blog/changes-for-2023-05-10/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Changes for 2023-03-23</title>
		<link>https://www.foxy.io/blog/changes-for-2023-03-23/</link>
					<comments>https://www.foxy.io/blog/changes-for-2023-03-23/#respond</comments>
		
		<dc:creator><![CDATA[Sami Fiaz]]></dc:creator>
		<pubDate>Sun, 23 Apr 2023 18:32:42 +0000</pubDate>
				<category><![CDATA[Changelogs]]></category>
		<guid isPermaLink="false">https://www.foxy.io/blog/?p=4976</guid>

					<description><![CDATA[Changes for 2023-03-23 • fix(add-user-form): add recaptcha in admin for `add-user` page • feat(square_up): update Square integration to only send 5 digit zips for the US]]></description>
										<content:encoded><![CDATA[<p>Changes for 2023-03-23<br />
• fix(add-user-form): add recaptcha in admin for `add-user` page<br />
• feat(square_up): update Square integration to only send 5 digit zips for the US</p>
]]></content:encoded>
					
					<wfw:commentRss>https://www.foxy.io/blog/changes-for-2023-03-23/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
	</channel>
</rss>
