Workspace header/footer code disappeared after update. Was this expected?

General
1

Hi everyone, I went into one of my older Pickaxe workspaces today and noticed that all of the code that used to be in my Settings > Header / Body / Confirmation Page sections appears to be gone.

This workspace previously had things like:

  • Facebook Pixel

  • Google tags / tracking scripts

  • affiliate program code

Now all of those fields are blank.

Screenshot 2026-03-31 at 6.57.09 PM
Screenshot 2026-03-31 at 6.57.09 PM3296×1856 300 KB

I’m trying to figure out whether this was expected after a recent Pickaxe update, or if that code is still stored somewhere else in the platform and just not showing up in the old location.

My main questions are:

  1. Were header/footer/custom code injections wiped during the update?

  2. Did Pickaxe move this information somewhere else?

  3. Do I need to manually set everything up again?

  4. If I re-add the scripts, is there any risk of duplicating something that may still be active in the background?

I’m attaching a screenshot of what I’m seeing. This is concerning because these scripts were important for tracking and affiliate functionality.

Would appreciate any clarification from the Pickaxe team or anyone else who has run into this.

2

Hey, another quick question about Pickaxe checkout and conversion tracking.

I installed a Meta Pixel manually in the global header of my Pickaxe workspace like I did before, and PageView events are coming through correctly in Meta Events Manager.

I also added a manual Meta Purchase event snippet to the “Confirmation Page Header” area in Pickaxe:

<script>
  fbq('track', 'Purchase');
</script>

But after testing a real checkout, I only see PageView events coming through, not Purchase.

My confusion is that after checkout, it seems like the flow may go straight into the member portal instead of showing a distinct confirmation / thank-you page first like it used to (I didn’t see one and the purchase event didn’t fire).

So my questions are:

  1. Does Pickaxe still use a real confirmation page after successful checkout?

  2. Does code placed in “Confirmation Page Header” still fire in the current checkout flow?

  3. If checkout now routes directly into the member portal, what is the correct place to fire a Meta Purchase event?

  4. Is there any supported way in Pickaxe to pass the actual purchase value dynamically to Meta Pixel?

Trying to make sure conversion tracking is set up correctly before running new ads or turning my old ones back on. I hope the update didn’t nuke conversion tracking via pixels. This is extremely important to scaling a sales campaign on facebook/ig. @danny_support @luna_support @abhi @lindsay_support

4

Hey I believe there was a reply to this last night from @luna_support but now it looks like it was deleted. Am I missing something? I just want to make sure the pixel for my older project is still setup on the backend even though it’s not showing in the settings.

Also it would be great if you could verify that the confirmation hook is going to be re-enabled before the portal redirect upon a completed checkout (super crucial to scaling a facebook ads campaign). I had a product launch that is basically paused until this gets fixed. If I cant get purchase events back to the ad account I can’t run ads. Any ETA on when this would be fixed so I can plan around it? @luna_support @danny_support @abhi @lindsay_support

Again, I’m a huge fan of pickaxe and love what you guys have built. Hopefully we can get this smoothed out soon so I can scale this new product.

5

Hi @motheraigaia ,

Thank you for your patience, and I apologize for the confusion here.

You are correct that there was a reply posted and then removed. Luna is our OpenClaw agent, and in some cases it can make mistakes or provide information that has not yet been fully verified. We removed that reply because it was not accurate, and I apologize for the mixed signals.

I have reported this properly to our engineering team, and it is now being tracked under ticket PRD-738. I understand how important this is for your launch and for conversion tracking, and I will keep you updated here as soon as more information becomes available.

Thank you again for your patience and for flagging this so clearly.

6

Thanks @danny_support . Can you verify if they are going to be putting the confirmation page back? I just want to know if I should wait for this to get fixed or if I need to figure out another way to get the conversion event back (or if that’s even possible). Nuking ads tracking on our studios should really be rethought if that’s the direction you are going. I’m pretty much stuck right now so any info would really be appreciated. I had a big budget for this upcoming campaign and not being able to optimize for purchases is basically useless. I really hope this gets fixed. Super bummed out about this.

7

Hi @motheraigaia ,

Thank you for your patience, and I apologize for the confusion.

We were able to find a Studio associated with your account where the custom code is still present. We found it under Pages → Home → Custom Code, and also under Portal → Edit Portal → Design → Custom Code.

Could you please share the specific Workspace or Studio link you are referring to? This will help us confirm we are investigating in the right place.

Regarding the confirmation page after checkout, I have raised that issue to our engineering team and they are currently looking into it as well.

Thank you again for your patience and understanding.

8

Thanks for your help, @danny_support . I can confirm the custom code is visible on that account, so that part is good.

The bigger concern I’m trying to get clarity on is whether Pickaxe is going to re-enable the confirmation page behavior after checkout.

Previously, this worked by placing the purchase event code snippet under Settings → Confirmation Page Header. When a customer successfully checked out and hit that confirmation page, the Facebook pixel would fire the purchase event and send the conversion back to Meta Ads correctly. This was working well before the update.

That setting still appears to exist at Settings → Confirmation Page Header, but based on my testing, it does not seem to be functioning the way it did before.

Since Pickaxe does not currently offer server-side tracking or support for setting up the Conversions API, the confirmation page is critically important. Without it, there is no reliable way for the pixel to report that a successful purchase occurred. That means purchase conversions cannot be tracked properly in Facebook Ads.

I want to stress that this is not a minor issue. I’ve scaled Facebook ad campaigns to 7 figures, nearly 8, and accurate purchase tracking is absolutely essential if you want to run and scale campaigns successfully. Without a functioning purchase event, it becomes extremely difficult, and in many cases impossible, to scale efficiently.

The solution could be very simple: after checkout, have the confirmation page fire before redirecting the customer to the members portal. That alone would restore the ability to track purchases through the pixel.

My concern is that the importance of this may be getting overlooked, so I want to ask as clearly as possible:

Are you planning to re-enable the confirmation page behavior so purchase events can fire properly again, or not?

If not, I need to seriously rethink what I’ve built here, because the ability to track purchase events was one of the main reasons I chose to build on Pickaxe instead of another platform. I genuinely believe some Pickaxes will be able to scale into the millions, but that only works if we can properly run and optimize paid ads.

9

Hi @motheraigaia ,

Yes, our engineering team is already working on this, and the intention is to restore the confirmation page behavior so purchase events can fire properly again after checkout.

I understand how important this is for conversion tracking, and I will update this thread as soon as the fix has been deployed.

10

@danny_support nice! Thanks so much for the confirmation. If you need me to run a test once it has been implemented let me know. Keep me updated, thanks again for the great news.