generateStaticParams and getStaticProps are not for the same thing. generateStaticParams handles the thing that getStaticPaths handles

The equivalence of getStaticProps in the app router is (statically rendered) server components

you are right, my question was wrong, of course I meant getStaticPaths vs getStaticParams

I don’t really understand your question. Can you show the pages router code that you use for this case?

export default async function Product({ params: { slug } }) {
const prodraw = await fetch("https://abcdefg.abc/api/route?slug=" + slug, {
next: { tags: [slug] },
});
const product = await prodraw.json();

const termslug= product.termslug
}

export async function generateStaticParams() {
const res = await fetch("https://abcdebf.abc/api/anotheroute");
let slugs = await res.json();

return slugs.map((slug) => {
return {
slug: slug,
};
//}
});
}

Is there a way I can pass another param from generateStaticParams that is accessible in my function to use it as a second revalidation tag?

Something like that ?
https://nextjs.org/docs/app/api-reference/functions/generate-static-params#generate-params-from-the-bottom-up

I think this is what you are looking for

in theory yes, but I do not want another subroute, and the second key is only available when there is another subroute

Can a second fetch before the existing one works for you to get that param ?

(I mean inside the component)

I understand that and it works, but I thougt there is maybe a solution where I do not need to add another fetch